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

v0.3.0

Published

Add CDN hosts to all your static assets. Supports relative path in CSS files

Downloads

4

Readme

grunt-cdner

Add CDN host to the path of all your static assets

Getting Started

This plugin requires Grunt ~0.4.5

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-cdner --save-dev

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

grunt.loadNpmTasks('grunt-cdner');

The cndify task

Overview

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

grunt.initConfig({
  cdner: {
    options: {
      cdn: '//example.com'
      ignore: [],
      root: 'dest',
      htmlExtension: 'html'
    },
    your_target: {
      // Target-specific file lists and/or options go here.
      // make sure you have separate file lists for your CSS and HTML files
    }
  }
})

Options

options.cdn

Type: String Default value: ''

A string value that is added as a host to all your static assets.

options.htmlExtension

Type: String Default value: 'html'

The extension of html assets. This is useful if you use a templating language for your html where you want to cachebust assets, i.e. 'handlebars'

options.ignore

Type: Array Default value: []

Array of strings that if found in the path are not modified. This is useful if you have some assets that are not hosted on a CDN.

options.root

Type: String Default value: ''

String that represents the root of the server, i.e. if your files are served out of a dist directory, you need to set the root to dist. This is to resolve relative paths correctly.

Usage Examples

options.cdn

grunt.initConfig({
  cdner: {
    options: {
      cdn: '//my.cdn.example.com',
      ignore: [
        '//3rd-party.cdn.example.com'
      ],
      htmlExtension: 'htm',
      root: 'dest'
    },
    build: {
      files: {
        'dest/default_options.css': ['src/testing.css'],
        'dest/default_options.htm': ['src/testing.htm']
      }
    }
  }
})

In this example, we defined the cdn option that will be added to all the static paths. URLs that contain //3rd-party.cdn.example.com are not modified. So if the testing.css or testing.htm files have content such as

h1 {
  background-image: url('testing.png');
}
h2 {
  background-image: url('//3rd-party.cdn.example.com/testing.png');
}

or

<script src="testing.js"></src>
<script src="//3rd-party.cdn.example.com/testing.js"></src>
<link href="testing.css" rel="stylesheet">
<img src="testing.png">

the generated result would be

h1 {
  background-image: url('//my.cdn.example.com/testing.png');
}
h2 {
  background-image: url('//3rd-party.cdn.example.com/testing.png');
}

or

<script src="//my.cdn/example.com/testing.js">

</src>
<script src="//3rd-party.cdn.example.com/testing.js"></src>
<link href="//my.cdn/example.com/testing.css" rel="stylesheet">
<img src="//my.cdn/example.com/testing.png">

N.B: if root hadn't been set to dest, the resulting path would be //3rd-party.cdn.example.com/dest/testing.png for a path of testing.png!!!

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

  • 2019-07-31 v0.3.0 add support for svg and inline background images. (Contributed by @evanderson)
  • 2016-02-28 v0.2.0 add support for Grunt 1.0.0 by updating peer dependencies
  • 2014-05-27 v0.1.0 initial release