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 🙏

© 2026 – Pkg Stats / Ryan Hefner

generator-angular-polymer

v0.1.1

Published

This project bridges the gap between **[Angular](https://angular.io)** and **[Polymer 1.x](https://www.polymer-project.org/)**. Therefore `generator-angular-polymer` is a [Yeoman generator](http://yeoman.io/) which creates directives to deal with issues b

Readme

Angular-Polymer Generator

This project bridges the gap between Angular and Polymer 1.x. Therefore generator-angular-polymer is a Yeoman generator which creates directives to deal with issues between current Angular and Polymer versions.

Note: Parts of this project base on angular-polymer.

Getting Started

  1. Configure the generator for your project setup (see Configuration).
  2. Run yo angular-polymer to create directives.
  3. Integrate the created directives in the existing Angular project. They are stored within the configured out-dir.

Demo App

The demo project shows an example usage of the generator with Angular 4 and angular-cli.

Installation

This project is part of the Yeoman environment and requires a current Yeoman version installed. To install Yeoman run:

npm install -g yo.

For more informations about Yeoman see the Yeoman documentation.

Afterwards, install the generator globally with:

npm install -g generator-angular-polymer

or local with:

npm install --save-dev generator-angular-polymer

Configuration

The generator's configuration is stored within the Yeoman configuration file (.yo-rc.json). Run yo angular-polymer:init inside the root directory of your project which creates an initial configuration of the generator.

The configuration file is located in the project's root directory and provides the following configuration parameters:

| Parameter | Function | | ------------- |-------------| |html-imports|List of all paths which contain Polymer elements.| |out-dir|Relative path to a directory in which the generatered directives will be stored.| |excluded|List of all elements that should not be part of the generation process.|

Best Practices

Use "Wrapper Files"

It's helpful to use one file which includes the Polymer elements into the Angular application and configures the generator, too. Since the file paths of Polymer elements don't exist twice, these wrapper files minimalize the configuration overhead.

Use the global POLYMER_ELEMENTS constant

It's possible but not to recommended to separately include Polymer elements instead of using the global POLYMER_ELEMENTS constant. This constant encapsulates all necessary files and gets recreated with every generator run.

License

Apache License 2.0