Create section on CSP for new build guide
Old docs with discussion of CSP: https://www.polymer-project.org/1.0/docs/tools/optimize-for-production#content-security-policy
-
[ ] 1. Note that Vulcanize has been replaced with Polymer Bundler https://github.com/Polymer/polymer-bundler
-
[ ] 2. Remove refs to Vulcanize and replace with refs to Polymer Bundler
-
[ ] 3. Create Polymer Bundler equivalent example for this command:
vulcanize elements/elements.html --inline-script | crisper --html elements/elements.vulcanized.html --js elements/elements.vulcanized.js
- [ ] 4. Create Polymer Bundler equivalent for working with gulp and crisper:
var gulp = require('gulp');
var vulcanize = require('gulp-vulcanize');
var crisper = require('gulp-crisper');
gulp.task('vulcanize', function() {
return gulp.src('app/elements/elements.html')
.pipe(vulcanize())
.pipe(crisper())
.pipe(gulp.dest('dist/elements'));
});
gulp.task('default', ['vulcanize']);
- [ ] 5. Find out whether anything has changed from "Is concatenation a good idea?" section
@justinfagnani May I have your help with points 3, 4 and 5 above pls?
@justinfagnani Would you be able to comment on these items, or suggest someone else who could? Alternately, let me know if this issue is not relevant and I'll close it. Thanks!
It would be great to get some attention on this issue. At the moment I'm unable to progress it. Is there someone who can help?
@FredKSchott @arthurevans @usergenic @justinfagnani
One thing to improve when updating the docs is to give a command for a typing polymer setup. In the source tree one will have an entrypoint ('index.html') and a shell ('src/myapp.html'). Building a bundled version will have 'build/bundled/index.html' and 'build/bundled/src/myapp.html'. This happens using the polymer-cli. Now whatever is the state-of-the art crisper replacement should not use some hypothetical 'elements/elements.html', but e.g. 'build/bundled/src/myapp.html'. Ideally have a sample project along with the docs.