Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Move babel-standalone into main Babel repo #6029
@hzoo and I both had the idea of showing a link to a copy of the REPL for every pull request in this repo, to allow pull requests to be more easily tested. Since the REPL uses
What I've done:
One thing that I haven't worked out yet is that the file size is varying significantly. When I build this on my computer, the version of babel-standalone built by this build process is about 1 MB larger than the one I build via the babel-standalone repo (5.58 MB vs 4.54 MB), which itself is much larger than the v6 version of babel-standalone (1.78 MB).
Building babel-standalone as part of the CircleCI build slows it down a bit, but once we upgrade to CircleCI 2.0 we could run the tests and the babel-standalone builds in parallel to improve things a bit.
Also note that I have not moved
Still to be done:
referenced this pull request
Jul 31, 2017
It only bundles Babel, and then Babel pulls in whatever other dependencies it needs (such as Babylon). It's hard to bundle a dev version of Babylon here since it'd need to link things across multiple Git repos. Using
The main outstanding issue with this is that the resulting file is much larger than the one built from the separate babel-standalone repo. I was going to try to fix this, but I can't build Babel on my computer at the moment (I'm currently blocked by yarnpkg/yarn#4106). I'll take a look once I figure out how to unblock myself.
This was referenced
Aug 8, 2017
@hzoo yes, it would be simpler. I'm not particularly against it, I was just saying that it's good to have the distinct repos because of two different usages.
I guess it would become a package, right? We could make create a
I unblocked my local Babel build by disabling Yarn workspaces in the Lerna config.
I think I worked out that the issues I'm seeing with file size are caused by the fact that multiple different packages reference common packages (like lodash). Since Webpack doesn't include the dedupe plugin any more, it's no longer deduping these, and thus each one has its own copy of Lodash. There's like 10 different copies of Lodash in the Webpack bundle.
Based on webpack/webpack#3266 and webpack/webpack#985, it sounds like