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

yeoman-blueprints

v1.0.6

Published

Extend yeoman.generators to add methods to interacting with local templates or blueprint

Downloads

22

Readme

yeoman-blueprints

For a working example look at generator-angular-blueprints.

Extends Yeoman's NamedBase to allow to your generator to use overridable templates. By using these extended methods yeoman will automatically check for locally created template under first ./blueprints and then ./node_modules before falling back to the global templates in the generator.

YOUR GENERATORS MUST BE UNDER generators/
npm install --save yeoman-blueprints

the generated folder structure for overriding blueprint

root
|-- blueprints
|---- templates
|------ blueprint.json
|------ controller
└-------- template.js

Methods

blueprints.copyTpl

// 'controller' - points to generator you want to use in this case located under generators/controller/
// 'js'         - the file type to be created
// values       - an object of values to be made available to template
this.copyTpl('controller', 'js', './destination/my-controller.js', values);

blueprints.copy

// 'controller' - points to generator you want to use in this case located under generators/controller/
// 'js'         - the file type to be created
this.copy('view', 'html', './destination/my-view.html');

Example:

var blueprint = require('yeoman-blueprints');

module.exports = blueprints.NamedBase.extend({
  writing: function writing() {
    var destDir = './client/app/views/' + this.name + '.controller.js';
             
    // Set the template values
    var values = {value1: 'HelloWorld'}
           
    // Create the template
    this.copyTpl('controller', 'js', destDir, values);
  }
});