Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Figure out plan for polyfilling library functionality stage < 4 #8416
Now that we've removed the stage presets, there's still the question of how we want to handle stage < 4 proposals for library functionality, rather than syntax.
In Babel 6 (and 7 for now), we just load
Given the precedent for
which would likely be enough?
As with syntax, this would also things safer for us as proposals evolve over time, because we can leave the existing polyfill files, but add additional ones alongside when things change.
Yeah I think we can emulate what we are doing with proposals in transforms?
So in v7 "import "@babel/polyfill" is only what is Stage 4? and opt into specific ones.
later: I guess the other question (really need to think about this), is whether we really need the alias if it's just core-js (also related is switching out core-js for other polyfills for transform-runtime/preset-env)