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

grunt-systemjs-pluginbuilder

v0.1.1

Published

A grunt systemJS build tool task to create plugin based bundles

Downloads

5

Readme

grunt-systemjs-pluginbuilder

A grunt systemJS build tool task to create plugin based bundles.

Travis Status

Issues & feature requests

This grunt task is just a wrapper for the node module called systemjs-pluginbuilder. If you have any issues or feature requests, please consider if this may belongs to the node module its self.

Getting Started

If you haven't used grunt before, be sure to check out the Getting Started guide.

From the same directory as your project's Gruntfile and package.json, install this plugin with the following command:

	npm install grunt-systemjs-pluginbuilder --save-dev

Once that's done, add this line to your project's Gruntfile:

	grunt.loadNpmTasks('grunt-systemjs-pluginbuilder');

Inside your Gruntfile.js file add a section named pluginbuilder. This section specifies the tasks. Each task takes sources and options as parameters.

Options

builder

This defines the builder which should be used. There are currently two possible values: systemjs and jspm. Each value refers to a specific builder:

The default value of this option is systemjs.

Attention: When using jspm as builder, the configPath option will be ignored. The builder uses the configured path to the config file inside the package.json. You also should not rewrite the baseURL property using the config option. This value can be defined in the package.json as well.

	builder: 'systemjs'

configPath

This sets the path to the systemjs config file. This is option is required when using the systemjs builder.

	configPath: 'js/src/config.js'

config

This option allows to add or overwrite settings from the loaded config file.

	config: {
		paths: {
			'app/*': 'js/src/*'
		}
	}

basePath

This is the path to the base file. The path should be defined as string. This option is required.

	basePath: 'js/src/Base.js'

pluginPaths

This is a list of all plugin files. The build of these files will have a substracted module tree of the base file. The paths will be defined as array of strings.

	pluginPaths: [
		'js/src/PluginA.js',
		'anywhere/else/src/PluginB.js'
	]

out

This defines the relative output path for built base and plugin files. The path is defined relative to each source file (defined by basePath and pluginPaths). The default value is '../build/'.

	out: '../build/'

Example: When using ../build/ as out option, with js/src/Base.js being the location of the base file, the build process will output to js/build/Base.js.

Configuration Example

	pluginbuilder: {
		all: {
			options: {
				builder: 'systemjs',
				configPath: 'js/src/config.js',
				config: {paths: {
					'app/*': 'js/src/*'
				},
				basePath: 'js/src/Base.js',
				pluginPathes: 'js/src/Plugin*.js',
				out: '../build/'
			}
		}
	}

Contribution

Tests & Validation

Run grunt to validate and run the tests.

License

LICENSE (MIT)