exhibit-builder-concat
v0.2.0
Published
Concatenates scripts and stylesheets based on adjacency of HTML tags
Downloads
4
Readme
concat
Exhibit.js builder plugin
Concatenates scripts and stylesheets based on adjacency of HTML tags.
$ npm install -D exhibit-builder-concat
Usage
.use('concat')You don't need to specify 'build blocks' like in Usemin/Useref. This builder automatically concatenates whatever it can – if two or more adjacent script elements (or stylesheet link elements) are found, with local URLs, they will be concatenated.
<html>
<head>
<link rel="stylesheet" href="some/file.css">
<link rel="stylesheet" href="another/file.css">
<link rel="stylesheet" href="third/file.css">
<link rel="stylesheet" href="http://example.com/some-external-file.css">
</head>
<body>
<h1>demo</h1>
<script src="http://jquery.com/jquery.js"></script>
<script src="local-script.js"></script>
<script src="another-local-script.js"></script>
</body>
</html>...turns into something like this (plus the new asset files, of course):
<html>
<head>
<link rel="stylesheet" href="concat-fw8dy7.css">
<link rel="stylesheet" href="http://example.com/some-external-file.css">
</head>
<body>
<h1>demo</h1>
<script src="http://jquery.com/jquery.js"></script>
<script src="concat-as8fgh.js"></script>
</body>
</html>Notes:
'Adjacent' means the tags have only whitespace or comments between them, nothing else.
All incoming CSS and JS files coming into the builder are blocked from going through. But when an HTML file is passed in, any assets are imported and then output in concatenated bunches. So if you don't actually reference a given script/stylesheet from any HTML file, it will not make it through this builder.
The output path names are in the form
concat-DIGEST.EXT, where DIGEST is an MD5 digest of all the normalized URLs of the concatenated assets.In general, you should use this builder after any preprocessors and script bundlers, and just before JS/CSS minifiers.
License
MIT