Split inline scripts from an HTML file for CSP compliance
Command line usage:
cat index.html | crisper -h build.html -j build.js
crisper --source index.html --html build.html --js build.js
crisper --html build.html --js build.js index.html
The output html file will load the output js file at the top of <head> with a <script defer> element.
Optional Flags:
--script-in-head=false- in the output HTML file, place the script at the end of
<body> - Note: Only use this if you need
document.writesupport.
- in the output HTML file, place the script at the end of
--only-split- Do not write include a
<script>tag in the output HTML file
- Do not write include a
--always-write-script- Always create a .js file, even without any
<script>elements.
- Always create a .js file, even without any
Library usage:
var output = crisper({
source: 'source HTML string',
jsFileName: 'output js file name.js',
scriptInHead: true, //default true
onlySplit: false, // default false
alwaysWriteScript: false // default false
});
fs.writeFile(htmlOutputFileName, output.html, 'utf-8', ...);
fs.writeFile(jsOutputFileName, output.js, 'utf-8', ...);When using vulcanize, crisper can handle the html string output directly and write the CSP seperated files on the command line
vulcanize index.html --inline-script | crisper --html build.html --js build.js
Or programmatically
vulcanize.process('index.html', function(err, cb) {
if (err) {
return cb(err);
} else {
var out = crisper({
source: html,
jsFileName: 'name of js file.js',
scriptInHead: true, // default true
onlySplit: false, // default false
alwaysWriteScript: false //default false
})
cb(null, out.html, out.js);
}
});- Deprecated
splitAPI was removedrequire('crisper').split()
- Default value of
script-in-headflag changed to true- This improves load performance by parallelizing HTML and script parsing
- This will break
document.writecalls - If you experience problems, you can use
--script-in-head=falseargument orscriptInHead: falsein library usage.