Assetflow is an asset deployment tool for node. It enables you to create powerful asset flows easily and fast.
Assetflow is a Grunt task and works with S3 out of the box. It will take care of versioning and apply solid cache-busting techniques transparently.
If you are not familiar with Grunt check out the Grunt's Getting Started guide.
A typical deployment flow using assetflow:
manifest.json file.HEAD operations with S3 and compare hashes using S3's ETAG.ETAG.Optionally there are two more tasks you can perform:
__ASSET(img/logo.jpg).clientManifest.js file, a client optimized subset of the manifest.npm install assetflow --save-dev
Open your Gruntfile and add the following config:
assets: {
options: {
manifest: 'temp/manifest.json',
},
all: {
src: ['assets/**'],
dest: 'temp/assets'
},
},
assetsS3: {
options: {
checkS3Head: true,
manifest: 'temp/manifest.json',
key: config.aws_key,
secret: config.aws_secret,
bucket: config.aws_static_bucket,
access: 'public-read',
},
target: {
upload: {
src: 'temp/assets/**',
dest: 'assets/'
}
}
}
assetsThe assets task performs these operations:
manifest.json file.
When this task finishes all your assets have been copied to a new temporary folder that you defined. This folder will contain your assets renamed with their own hash, like so:
app.js --> app-h522md41d.js
The manifest.json file generated by this task keeps a reference to all your assets so their names can be properly resolved in all environments.
manifestType: string Default: manifest.json
Define the location of the manifest file.
cdnurlType: string Default: none
Add the url of your CDN to prepend it to all assets.
relType: string Default: none
The rel option will perform directory subtraction on the source to calculate the relative path to the asset. Consider this case:
Your folder of static assets is under assets/, so the path to your logo would be assets/img/logo.png which would be accessed by the browser as /img/logo.png.
Declaring the assets folder as a rel path will make sure that all assets have the proper url.
Example
assets: {
options: {
rel: 'assets/'
},
all: {
src: 'assets/**',
dest: 'temp/assets'
}
}
truncateHashType: number Default: none
The md5 hash is 32 bytes long, you don't need all of it, use this option to truncate the hash down to n chars.
prependType: string Default: none
This option will prepend a value to the asset's key. It is mostly used to prepend a slash and make the asset key absolute, for example:
By default, the assets task will create records in the manifest.json file as relative web paths: img/logo.png. If you need the key to be an absolute path then you have to use prepend.
options: {
prepend: '/'
}
maxOperationsType: number Default: 100
The maximum number of concurrent operations, in this case the operations are file copying.
Set this to 0 to disable throttling. Set it to 1 to make all operations serial.
progressType: boolean Default: false
A fancy progress bar.
debugType: boolean Default: false
Print extra debugging information.
Here's an annotated configuration for the assets task:
assets: {
// global task options
options: {
// don't output debug information
debug: false,
// trancate the hash length to 8 chars.
truncateHash: 8,
// define the location of the manifest file.
manifest: 'temp/manifest.json',
// define the location of the cdn.
cdnurl: 'http://d3s3z9buwru1xx.cloudfront.net/assets/',
// Set maximum number of file copying concurent operations.
maxOperations: 100,
// Show a fancy progress indicator
progress: true,
// Set path to substract so the relative path for the assets can be calculated.
rel: 'lib/'
},
all: {
// local task options
options: {
// change the rel path to test/case
rel: 'assets/'
},
src: [
// all files under folder assets
'assets/**',
// except all files in less folder
'!assets/less/**',
// except all files in handlebars folder
'!assets/handlebars/**'
]
}
}
assetsReplaceThe assetsReplace task will search and replace the contents of your assets. It is useful for cases where you don't have the ability of a 'helper' to resolve your assets.
LESS files are a typical example, use a custom keyword to include your assets and run the assetsReplace task to populate the asset urls in your .less files. For example if the custom keyword is __ASSET():
@bg-dot-light: url(__ASSET(img/pdf-icon-cv.png)) repeat 0 0 #2a2a2a;
After the assetsReplace task is executed the same line will look like this:
@bg-dot-light: url(http://d3s3z9buwru1xx.cloudfront.net/assets/img/pdf-icon-cv-fk44j2s.png) repeat 0 0 #2a2a2a;
The
assetsReplacetask is based on grunt-string-replace by @erickrdch
manifestType: string Default: manifest.json
Define the location of the manifest file.
keyType: string Default: none
Define the keyword that will be searched for replacement. Use the % char as a placeholder for the asset name. e.g.:
options: {
key: '__ASSET(%)'
}
keyRegexType: string Default: none
Use this to define a regex as a keyword. The type must be string, but the string will be evaluated as a regex. The % char is a placeholder for the asset name and the reason why this option needs to be a string instead of a regex type.
So take case to double escape what you need escaped, e.g.
// this regex
var reg = /match[\s]space/;
// is represented like that as a string:
var strReg = 'match[\\\s]space';
prependType: string Default: none
This option will prepend a value to the asset's key. It is mostly used to prepend a slash and make the asset key absolute.
debugType: boolean Default: false
Print extra debugging information.
Here's an annotated configuration for the assetsReplace task:
assetsReplace: {
// global task options
options: {
// don't output debug information
debug: false,
// define the location of the manifest file.
manifest: 'temp/manifest.json',
},
// the less target
less: {
options: {
// define the keyword for this target
key: '__ASSET(%)'
},
files: {
// Search & replace all .less files under the assets/less folder
// and output the result in the temp/less folder
'temp/less/': ['assets/less/**/*.less']
}
},
// the handlebars target
handlebars: {
options: {
// a regex for lax matching {{asset "%"}} allowing for spaces in between
// and single quotes.
keyRegex: '\\\{\\\{[\\\s]*asset[\\\s]+[\\\'\\\"]{1}%[\\\'\\\"]{1}[\\\s]*\\\}\\\}',
// prepend the slash on every asset query
prepend: '/'
},
// all the files from the assets/handlebars folder
src: 'assets/handlebars/**/*.hbs',
// output to temp/handlebars folder
dest: 'temp/handlebars/'
}
}
assetsBundleThe assetsBundle task will create a compact version of the manifest file, optimized for transferring to the client as a javascript file. The manifest.json file is pretty large and not suited for getting transfered. Furthermore it might be the case where you have several hundreds, if not thousands of assets but you only need a handful to be consumed by your front-end app. This is the task that enables you to do this.
manifestType: string Default: manifest.json
Define the location of the manifest file.
amdType: boolean Default: false
export the assets as an AMD module.
nsType: string Default: ASSETS
Define a namespace to export using the global window Object. You can use dot notation.
assetsType: Array Default: []
An array of strings where you define the asset filename keys you want included.
debugType: boolean Default: false
Print extra debugging information.
Here's an annotated configuration for the assetsBundle task:
assetsBundle: {
// global task options
options: {
// define the location of the manifest file.
manifest: 'temp/manifest.json',
// export as AMD
amd: true
},
// Export as amd
amd: {
dest: 'temp/bundles/clientManifest.amd.js'
},
// Export using namespaces
ns: {
options: {
// Export assets on this global namespace:
ns: 'app.assets'
},
dest: 'temp/bundles/clientManifest.ns.js'
}
}
The javascript file generated by the assetsBundle task will export an Object that contains key value pairs to the assets. If you are using AMD to export the assets this is how you'd access them:
var assets = require('assets');
var asset = assets['/img/logo.png'];
// --> https://d3s3z9buwru1xx.cloudfront.net/assets/img/logo-fh422j4f.png
This is a weak part in the API and will surely see changes in the future.
assetsS3The assetsS3 task will read the manifest.json file and upload all the assets to S3. Although it's optional, it is highly advised to use the chechS3Head option which enables md5 hash checking between S3 and your local files.
The
assetsS3task is based on grunt-S3 by @pifantastic. All options from that task are available in this one too.
These are the options that are only available in the assetsS3 task of Assetflow.
manifestType: string Default: manifest.json
Define the location of the manifest file.
checkS3HeadType: boolean Default: false
Perform md5 hash comparisons between the local assets and the ones in S3. It is highly advisable that you enable this option so you only upload files that have been updated.
relType: string Default: none
The rel option will perform directory subtraction on the source to calculate the relative path to the asset.
maxOperationsType: number Default: 100
The maximum number of concurrent operations, in this case the operations are network uploads.
Set this to 0 to disable throttling. Set it to 1 to make all operations serial.
progressType: boolean Default: false
A fancy progress bar.
debugType: boolean Default: false
Print extra debugging information.
These options are available by Grunt-S3, sic:
The grunt-s3 task is now a multi-task; meaning you can specify different targets for this task to run as.
The following are the default options available to each target.
{ 'X-Awesomeness': 'Out-Of-This-World', 'X-Stuff': 'And Things!' }private, public-read, public-read-write, authenticated-read, bucket-owner-read, bucket-owner-full-control['.jpg', '.jpeg', '.png'].src
and a dest. Any of the above values may also be overriden.src and a dest. Any of the above values may also be overriden.src to delete from s3. Any of
the above values may also be overriden.Here's an annotated configuration for the assetsS3 task:
assetsS3: {
options: {
// no debug info
debug: false,
// enable checking md5 hashes by performing S3 HEAD requests.
checkS3Head: true,
// the manifest file
manifest: 'temp/manifest.json',
// aws credentials
key: 'AWS-KEY',
secret: 'AWS-SECRET',
bucket: 'S3-BUCKET',
// Enable public access
access: 'public-read',
// don't show the fancy progress indicator.
progress: false
},
all: {
// These options override the defaults
options: {
// limit concurent uploads to 100
maxOperations: 100
},
// the 'upload' option key is required
upload: {
// all files from temp/assets
src: 'temp/assets/**',
// a prefix folder on S3
dest: 'assets/',
// the rel option
rel: 'temp/assets/',
// gzip uploaded files
gzip: true,
// excluded these extensions
gzipExclude: ['.jpeg', '.jpg', '.png', '.gif', '.less', '.mp3',
'.mp4', '.mkv', '.webm', '.gz'],
// upload assets with a looong expire Cache-Control header.
headers: {'Cache-Control': 'max-age=31536000, public'}
}
}
}
FAQs
Asset deployment for node
The npm package assetflow receives a total of 4 weekly downloads. As such, assetflow popularity was classified as not popular.
We found that assetflow 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.