-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Upgrade bundling #2187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade bundling #2187
Changes from 4 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,16 +84,29 @@ module.exports = { | |
testContainerHome: '/var/www/streambed/image_server/plotly.js', | ||
|
||
uglifyOptions: { | ||
fromString: true, | ||
mangle: true, | ||
compress: { | ||
warnings: false, | ||
screw_ie8: true | ||
warnings: false | ||
}, | ||
output: { | ||
beautify: false, | ||
ascii_only: true | ||
} | ||
}, | ||
sourceMap: false | ||
}, | ||
|
||
bubleifyOptions: { | ||
target: { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm. We have to target browsers waaaaaaaay older than that. Can bubleify guarantee to output code that IE11 understands? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @etpinard that is the best bubleify can do, it is targeted only for ES6 → ES5, not ES5 → ES3. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm. Well that won't work then. plotly.js needs to be pure ES5. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @etpinard that is pure ES5, same as what we have now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could we put these config options in the package.json instead, so that all consumers bundling with browserify or webpack+ify-loader get the same results as us in our There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can the output bundle be minified by plain-old uglify-js? e.g. does
work? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not a big fan of this |
||
chrome: 48, | ||
firefox: 44, | ||
edge: 12 | ||
}, | ||
transforms: { | ||
arrow: true, | ||
defaultParameter: false, | ||
dangerousForOf: true, | ||
}, | ||
sourceMap: false | ||
}, | ||
|
||
licenseDist: [ | ||
|
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha nice catch. That's for that
spawn('npm', ['ls', '--json', '--only', 'prod']);
statement below - which will be obsolete when we switch tonpm@5
as the newpackage-lock.json
file will do that same as the currentdist/npm-ls.json
.