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

smush-components

v0.1.4

Published

Grunt tasks that takes all js and css from ./components and combines them. Does not use requirejs.

Downloads

4

Readme

grunt-smush-components

Grunt task for concatinating components assets into single files. This task relies on the 'main' key in your components.json to figure out which files are relevant. With the fileMap option, you can then create a map between a files extension and the destination output file. This project does not use requirejs or AMD It simply concatinates your files together.

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-smush-components --save-dev

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

grunt.loadNpmTasks('grunt-smush-components');

If the plugin has been installed correctly, running grunt --help at the command line should list the newly-installed plugin's task or tasks. In addition, the plugin should be listed in package.json as a devDependency, which ensures that it will be installed whenever the npm install command is run.

The "smush-components" task

Overview

In your project's Gruntfile, add a section named smush-components to the data object passed into grunt.initConfig().

grunt.initConfig({
  'smush-components': {
    options: {
      fileMap: {
        js: './public/js/components.js',
        css: './public/css/components.css'
      }
    }
  },
})

Options

options.fileMap

Type: Object Default value: { js: 'components.js', css: 'components.css' }

Map all files of a specific extension to a destination file

Usage Examples

Lazy Example

This will output to ./components.css and ./components.js

grunt.initConfig({
  'smush-components': {}
})

Custom Options

Outputs files according to the fileMap

grunt.initConfig({
  'smush-components': {
    options: {
      fileMap: {
        js: './public/js/components.js',
        css: './public/css/components.js'
      }
    }
  }
})

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.

Release History

(Nothing yet)