npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ng-guzzle

v0.0.36

Published

A build tool for AngularJS SPAs.

Downloads

4

Readme

ng-guzzle

This project helps me remove the gulp boilerplate from my AngularJS applications. You're welcome to use it, but I don't have any intention of writing documentation at the moment. There is, however, a partial example.

Ok, here are some reminders for myself:

$ guzzle init
$ guzzle build
$ guzzle watch

package.json

...
  "dependencyConfig": {
    "ng-guzzle": {
      "liveServerParams": {
        "port": 3000,
        "etc.": "etc."
      },
      "modules": [
        {
          "id": "app",
          "src": "./src/app/",
          "dest": "./dest/",
          "static": "./dest/",
          "strictDi": false,
          "minify": false
        },
        {
          "id": "lib",
          "src": "./src/lib/",
          "dest": "./dest/"
        }
      ]
    }
  }
...

Each guzzle module gets compiled into two files: one JavaScript file and one CSS file. Each JavaScript module is wrapped in an IIFE with a single parameter named ngm. This parameter is an Angular module. The Angular module can be bootstrapped by including a selector attribute on the script tag used to include the JavaScript file. There are two possible values for the selector attribute: document | [QUERY SELECTOR]. If you use the query selector and the selector returns multiple elements, the Angular module will be bootstrapped on all elements returned by the selector query.

index.html

...
  <script src="/dest/app.js" selector="document"></script>
...