Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@babel/parser CLI args #9931

Open
goodmind opened this issue May 1, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@goodmind
Copy link

commented May 1, 2019

Feature Request

Is your feature request related to a problem? Please describe.

@babel/parser has CLI, but I can't do much with it, it even doesn't read .babelrc

Describe the solution you'd like

Read .babelrc and infer parser options and have overridable CLI options

Teachability, Documentation, Adoption, Migration Strategy

Add options to docs

@babel-bot

This comment has been minimized.

Copy link
Collaborator

commented May 1, 2019

Hey @goodmind! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community
that typically always has someone willing to help. You can sign-up here
for an invite.

@nicolo-ribaudo

This comment has been minimized.

Copy link
Member

commented May 3, 2019

I think that this should be implemented in @babel/cli (e.g. babel --parse foo.js). @babel/pareser doesn't know about the config resolution logic, and implementing it there would led to a big size increase for almost no benefit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.