grunt-cdn-ideame
Advanced tools
Properly prepends a CDN url to those assets referenced with absolute paths (but not URLs)
Grunt plugin for properly prepending a CDN url to those assets referenced with absolute paths (but not URLs)
Install this grunt plugin next to your project's gruntfile with: npm install grunt-cdn
Then add this line to your project's grunt.js gruntfile:
grunt.loadNpmTasks('grunt-cdn');
Then specify your config:
grunt.initConfig({
cdn: {
dist: {
/** @required - string (or array of) including grunt glob variables */
src: ['./static/*.html', './static/*.css', './static/*.soy'],
/** @optional - if provided a copy will be stored without modifying original file */
dest: './dist/static/',
/** @required - root URL of your CDN (may contains sub-paths as shown below) */
cdn: 'http://cdn.cloudfront.net/container/'
}
}
});
With the following input
<!DOCTYPE html>
<html>
<head>
<title>Mural.ly</title>
<link rel="stylesheet" type="text/css" href="/static/compiled.css?v=13512tyu3kds" />
</head>
<body id="landing-page">
...
</body>
</html>
After running the task the output looks like
<!DOCTYPE html>
<html>
<head>
<title>Mural.ly</title>
<link rel="stylesheet" type="text/css" href="http://cdn.cloudfront.net/container/static/compiled.css?v=13512tyu3kds" />
</head>
<body id="landing-page">
...
</body>
</html>
As you can see we maintain the "container" pathname in this case, and we also keep the original query strings. This task is really handy if you upload stuff from your CI to make it transparent to developers.
NOTE: This task only works with "absolute" paths. We consider paths starting with . (or ..) as relative, and with / absolute. We're using the same aproach as the *NIX file-system.
FAQs
Properly prepends a CDN url to those assets referenced with absolute paths (but not URLs)
We found that grunt-cdn-ideame demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
TC39 met in Seattle and advanced 9 JavaScript proposals, including three to Stage 4, introducing new features and enhancements for a future ECMAScript release.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.