Conversation
|
Hmm, I think CI needs to be updated to run |
sbc100
left a comment
There was a problem hiding this comment.
yes, we need to to do a couple of things before landing this:
- Have emsdk automatically run
npm installpost installation. - Teach our CI to run
npm install - Inform git users / developers that we now have this post-clone step.
I wonder if we are going have other steps (such as pip install or git submodule update), in which case it might make sense to wrap them in single ./bootstrap.sh/bootstrap.bat. Maybe that is thinking too far ahead and we should see how it goes with just npm install?
emscripten-core/emsdk#404 will resolve that. |
Added an error message explaining to run npm install to set up dependencies. |
cf3fd29 to
c31dd42
Compare
* Complete migration of stack overflow checks to library function in MINIMAL_RUNTIME, and add support for --separate-asm, MODULARIZE and ALLOW_MEMORY_GROWTH with MINIMAL_RUNTIME. * Use acorn-optimizer to minify <script> tags in .html code (TODO: Migrate to a better minifier, but needs one installed alongside the repository) * Remove manual JS code minification in HTML5, to use html-minifier-terser in PR #9990. * Update minimal_runtime test
3595e2f to
efb8d87
Compare
|
Brought this up to latest, and tests passing now - this is good for review and landing. |
cfcac9f to
f990de3
Compare
|
There seems to be a test failures with test_cubegeom_normal_dap_far_glda_quad (test_browser.browser) in Firefox but not in Chrome that pops up, I wonder if Firefox had regressed on something. Although the failure occurs only on CI, unable to reproduce locally. |
|
Re-running failing tests on circle to see if those flakes |
How important do you feel that is? I am working a bit tight now against our code freeze for 2020.01 release to try to squeeze new Emscripten compiler update in with as many features as I can. |
Well I guess we have decided to go down this route, but we are having issue with npm on the emscripten-releases builders right now, so perhaps at least wait until the dust settles there and we can cut a new emscripten release (I hope that will be today). |
1de47f4 to
ff6bb27
Compare
|
Yes the closure related issues have now (hopefully) been solved. But I did causes a lot of issues, mostly related to window. We just cut and emscripten release containing this change so we can see how it effects actual users. I suspect that closure will be the outlier here in terms of the fallout, since it has the native and java and js versions in there, and other dependencies should be pure JS. However, I would still rather let the dust settle a little before landing more npm dependencies. Could we at least wait a couple of days? |
…rop support for minifying JS code in it altogether, so migrate to using html-minifier-terser that can minify <script> content inside HTML files.
ff6bb27 to
3cf4a65
Compare
sbc100
left a comment
There was a problem hiding this comment.
Sorry.. I had this comment sitting there unsent..
|
Have we seen any issues with the use of npm in the wild @kripken? Are we ready to land this change which extends the npm usage do you think? |
|
This issue worries me: #10385 - something changed in closure compiler it seems, causing that project to break. But perhaps that doesn't need to block this. Worst case we can disable minification inside HTML files if problems occur (which is a risk I wouldn't suggest for core minification of the main JS). |
|
Right, that issue seems to be related to the closure upgrade rather than that fact that we used npm to install it. Good news that we can probably go ahead and land this when its ready. |
|
I don't think those errors are related to Closure update, but something has changed around __syscall3 function. |
9e107bd to
f02717d
Compare
* Complete migration of stack overflow checks to library function in MINIMAL_RUNTIME, and add support for --separate-asm, MODULARIZE and ALLOW_MEMORY_GROWTH with MINIMAL_RUNTIME. * Use acorn-optimizer to minify <script> tags in .html code (TODO: Migrate to a better minifier, but needs one installed alongside the repository) * Remove manual JS code minification in HTML5, to use html-minifier-terser in PR emscripten-core#9990. * Update minimal_runtime test
html-minifier was buggy in minifying JS code, and author decided to drop support for minifying JS code in it altogether, so migrate to using html-minifier-terser that can minify <script> content inside HTML files.
PR #9989 should land first, this is easier to rebase on top of that.