-
Notifications
You must be signed in to change notification settings - Fork 334
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
Run browser tests on minified code #3050
Conversation
Question: Do we need to keep the (unminified) |
a584518
to
92393a7
Compare
92393a7
to
ec9c647
Compare
dc5fe68
to
88d6f4f
Compare
ec9c647
to
25cef2a
Compare
96d4c8a
to
e0ed994
Compare
25cef2a
to
8aae7f8
Compare
e0ed994
to
16c4c00
Compare
8aae7f8
to
f1eec38
Compare
5eb4cbc
to
94bf08f
Compare
ac8b2b4
to
9abb62f
Compare
94bf08f
to
0c25266
Compare
9abb62f
to
286b148
Compare
0c25266
to
721b159
Compare
286b148
to
a612911
Compare
@36degrees This one is ready for review again |
721b159
to
7765b4a
Compare
a612911
to
faca548
Compare
Rebased with: |
We now compile to `all.min.js` to ensure our browser tests can run on minified code
For consistency, shows that file content is minified
faca548
to
356a30c
Compare
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.
LGTM.
This uncovers the fact that our minified JS (which we include in dist/
and include in the zip attached to each release) errors in IE8. I don't think that should block this (as it appears to be a pre-existing issue) – have raised #3136 to track separately.
Quick proof of concept to:
all.mjs
(for ./dist and ./public).min.*
extensions in webpack exampleDiscussed in:
Why?
Ensures our browser tests (via the review app) run on minified code as minifiers can cause their own issues:
Also gives us the confidence to swap to a modern ES6+ minifier: