A Webpack plugin to merge your files together, unedited, into a single file.
npm install webpack-raw-bundler
When you need to include a bunch of libraries, but don't have time to make the ordinary require statements, use this to bundle them all together so that their globals are actually global. In other words, From the old:
<script src="js/jquery.js"></script>
<script src="js/silly.js"></script>
<script>
$(silly()); // Some function in silly.js's global scope
</script>
To the new:
<script src="js/bundle.js"></script>
<script>
$(silly());
</script>
var RawBundlerPlugin = require('webpack-raw-bundler');
module.exports = {
plugins: [
new RawBundlerPlugin({
excludedFilenames: [/angulartics/],
readEncoding: "utf-8",
includeFilePathComments: false,
allowDuplicatesInBundle: false,
bundles: [ "vendor.js", "styles.css", "vendor.lib.js" ],
"vendor.js": [
'js/*.js'
],
"vendor.lib.js": [{
path: "../build/*.js",
match: /vendor/
}],
"styles.css": [
'css/bootstrap.css',
'css/edits.css'
]
})
]
This generates two files with merged js and css content.
<script src="./vendor.js"></script>
<link rel="stylesheet" href="./styles.css">
(Required)
The output files to be made. These will be outputted to the same directory as set in module.exports.output.path
of your webpack.config
(Required)
Must have the same name as a member of bundles. The sub-array are the files to are be included in the bundle. The sub-array has the following format options:
"bundle_name.extension" : [
"pathtype1.ext",
"*.ext",
{
path: "pathtype2.ext"
match: /Bad_file/ /* Overpowerd by the exlusion variable */
},
{ path: "*.ext2" }
]
If a path is given a wildcard, it will add all files, including all subdirectories, with the appropiate file extension from that folder on.
default: []
An array of regexp expressions that if a dynamically found filename is matched, will not be included.
default: utf-8
The encoding nodejs reads in. Look up the documentation for more information.
(Boolean) - default: false
Puts the file path of the added file in a /**/
comment style before the bundled file contents.
Note: If reading from an invlaid encoding type, ie: settings are utf-8 but file is encoded in utf-8-BOM, then you may seem some non-rendering character generated after this.
(Boolean) - default: false
Per individual file bundle, are identical file names allowed to be parsed?
Add support for `useAsLoader`
Add per bundle support for exlcusions
Add custom comment styles