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-jssourcemaprev

v1.0.0

Published

Change a sourcemap to match the name of a revved js file, and move the source locations to a revved folder so forever caching can be used.

Downloads

3

Readme

grunt-jssourcemaprev Build Status

Change a sourcemap to match the name of a revved js file, and move the source locations to a revved folder so forever caching can be used.

Getting Started

This plugin requires Grunt ~0.4.1

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-jssourcemaprev --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-jssourcemaprev');

The "jssourcemaprev" task

Overview

Revision a sourcemap and source files so they match an already revisioned and minified js file(s). You can revision the js assets with a plugin such as grunt-filerev. This is useful if you want to be able to debug on a live system where static files are cached such as with a CDN.

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

grunt.initConfig({
  jssourcemaprev: {
    options: {
      moveSrc: false // If true we move the src files, else we copy them. Copy is the default.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
      // Note that dest and ext will be ignored.
      // we are specifying js file locations which will be updated in place.
    },
  },
})

Options

options.moveSrc

Type: Boolean Default value: false

If true we move the src files, else we copy them. Copy is the default (false).

Usage Examples

Default Options

In this example, the default options are used to do take a peek inside files matching public/js/testing.*.js. It will:

  • Search for a sourceMappingURL in the file
  • Check if it can find the source map file
  • Change the source map name to match the js file name (sans the extension)
  • Update the js file to point to the renamed source map
  • Copy the files in the sourceRoot attribute of the source map to a directory matching the name of the js file (sans the extension).
  • Update the source map sourceRoot attribute to point to the new location.
grunt.initConfig({
  jssourcemaprev: {
    options: {},
    files: {
      src: ['public/js/testing.*.js'],
    },
  },
})

Custom Options

In this example, the same happens as in the default example except the files in the sourceRoot attribute of the source map are moved, not copied, to the location described in default options.

grunt.initConfig({
  jssourcemaprev: {
    options: {
      moveSrc: true,
    },
    files: {
      src: ['public/js/testing.*.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)