Update babel and webpack#2005
Conversation
mohd-akram
force-pushed
the
update-babel-webpack
branch
from
ddca385 to
2b4aa7e
Compare
mohd-akram
force-pushed
the
update-babel-webpack
branch
from
2b4aa7e to
50b6e3b
Compare
|
Node.js 12, 14 and 16 should be dropped from the CI for pushes and pull requests against master since they're all EOL. They can be kept for pushes and pull requests against the 4.x branch only. |
mohd-akram
force-pushed
the
update-babel-webpack
branch
2 times, most recently
from
5dbbce0 to
5fcac11
Compare
|
The plan is to use https://github.com/developit/microbundle and get rid of grunt, babel and webpack. If you wanna give it a try, please go ahead, otherwise please close it and wait for me to make the change. |
|
Is it possible to merge this in the meantime until a switch to microbundle is made, since I already have it working with minimal changes and this is a blocker to other improvements. Also, looking at microbundle, it does not seem to be very regularly updated, and I'm not sure how flexible it is. If, for example, we want a bundle with some polyfills (I have a version of this PR for 4.x with all that, but it hit a snag with AMD support). I don't love grunt or babel, and would rip them out too, but that's a more complex endeavor at this point. EDIT: Apparently it depends on Babel and rollup itself, and quite a few other dependencies. |
Remove wildcard and require tests since the library has a default export and that's what should be used for browser code.
mohd-akram
force-pushed
the
update-babel-webpack
branch
from
5fcac11 to
2fce11e
Compare
|
We'll add modern tooling soon. Closing this, since it is almost 3 years old and outdated. |
2 participants
Remove wildcard and require tests since the library has a default export and that's what should be used for browser code.
This is a prerequisite to #2004 and other potential enhancements.