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

generator-angular-widget

v1.3.0

Published

Generates everything necessary to begin work on a new shareable Angular module.

Downloads

3

Readme

generator-angular-widget

generator-angular-widget is a Yeoman generator for quickly creating the boilerplate for a shareable Angular module. These modules can be developed in isolation and later consumed by an independent host application.

This template uses SystemJS for script loading. Any consuming application will also need to use SystemJS.

Getting started

  • Install Yeoman, jspm, and generator-angular-widget globally: npm install yo jspm generator-angular-widget -g
  • Run the generator: yo angular-widget
  • Point your local development server at the dev-build directory

Sharing your widget

Once you have your Angular widget working in isolation, create a distribution build using gulp build-deploy. This will copy all relevant files into the dist directory, ready for consumption. Because these files will be consumed by other Angular apps before they are deployed to a live environment, no minification or concatenation is performed on these files. The application that consumes these files is responsible for concatenation/minification.

To use your widget in a host application, add your widget's module as a jspm dependency of the host:

jspm install my-widget=github:your-github-username/your-widgets-repo-name

Or, if using a private git server (for example, a private GitLab instace), create a custom jspm registry using jspm-git. For other use cases, see http://jspm.io/docs/registries.html.

Then, in your host application, you can import your widget's Angular module like so:

import {myWidgetModule} from 'my-widget';

let myHostModule = angular.module('HostModule', [myWidgetModule.name]);

Your host now has full access to your widget's module, as if the module lived directly in the host.

Troubleshooting

I'm getting a "fatal: Could not read from remote repository" error message when running jspm install. If you're behind a corporate proxy, you may need to create HTTP_PROXY and HTTPS_PROXY environment variables to allow jspm to fetch dependencies from GitHub.

I'm getting a "GitHub rate limit reached" error message when running jspm install. See http://stackoverflow.com/a/30995041/1063392. Make sure to give your access token the public_repo scope.

Some other notes

  • Any images or other assets (fonts, video, audio, etc) should not be placed at the root of app/assets; instead, they should be placed in app/assets/widget-name. See assets/WhereToPutAssets.md for more information.