Export babel tooling packages in @babel/standalone

[ajihyf]

Q	A
Fixed Issues?	Fixes #11599
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?	Yes
Tests Added + Pass?	Yes
Documentation PR Link	babel/website#2871
Any Dependency Changes?
License	MIT

I am implementing a tool to transform an expression using parser.parseExpression, traverse, types.X and generate(exp). This tool is used on the web browser however @babel/standalone doesn't export these toolings. Thus I want to directly export babel tooling in @babel/standalone(and @babel/core, since @babel/standalone just imports from it).

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/56343

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 4c0d45a:

Sandbox	Source
white-butterfly-gemdo	Configuration
hidden-thunder-5s2ty	Configuration

[NullVoxPopuli]

I ran in to a need for this today :)

[liuxingbaoyu]

Thanks!

[kungfooman]

This is very helpful and allows a better testing of all PRs directly in the console of babel-bot's web preview 🌈

[nicolo-ribaudo]

I dislike how this can create confusion between import { parse } from "@babel/core"; parse(...) and import { parser } from "@babel/core"; parser.parse(...), that do two completely different things.

Given that the need is only in @babel/standalone, how do you feel about only exposing them there as Babel.packages.parser, Babel.packages.generator, etc?

[liuxingbaoyu]

I agree with this!
Sorry I was wrong, I think this sounds good.

[liuxingbaoyu]

Given that the need is only in @babel/standalone

Does this mean doing this in @babel/core as well?
import { packages } from "@babel/core"; doesn't seem very good.

[NullVoxPopuli]

hm, I'm mostly hoping for a way to not using @babel/standalone, but would like to easily use @babel/core (and friends) to have a minimal browser-compiler with a set few plugins (rather than the all of them that standalone includes).

Last I tried this, it seemed some custom build was required (which isn't fun 😅 ), due to @babel/core assuming it's running in a node-like env (based on the access of process, etc)

[nicolo-ribaudo]

@liuxingbaoyu No, only for standalone. If you are using a bundler or running on Node.js, you can just import "@babel/parser" directly.

Last I tried this, it seemed some custom build was required (which isn't fun 😅 ), due to @babel/core assuming it's running in a node-like env (based on the access of process, etc)

@NullVoxPopuli We use browsers in package.json to provide alternatives to those files that use process&co. Do you have any suggestion of a better way to isolate Node.js-specific from browser-specific code? Would using imports as a semi-standard alternative to browsers be good enough?

[liuxingbaoyu]

Now this PR is no longer exported from @babel/core, but I think that doesn't matter and it can be treated as another issue.

[nicolo-ribaudo]

I don't think we should export them from @babel/core at all. If you are already using individual unbundled packages, you can just import @babel/parser&co directly.