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

Reconsider how --module and --type should work #115

Open
Avaq opened this issue Apr 2, 2019 · 1 comment
Open

Reconsider how --module and --type should work #115

Avaq opened this issue Apr 2, 2019 · 1 comment

Comments

@Avaq
Copy link
Collaborator

Avaq commented Apr 2, 2019

We might want to unify these two options to simplify the CLI. We might also want to consider that the esm module option could be inferred from the .mjs file extension. Currently inference only works to detect --type.

@danse
Copy link
Collaborator

danse commented Apr 9, 2019

I gave a quick look at this, just to keep a conversation going. At first glance it seems sensible to unify the two. As far as i understand the main areas of intervention are the option definition and validation. Any reason why not to unify the two options?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants