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

Nature code after eject #554

Closed
Jiansen opened this issue Sep 2, 2016 · 1 comment
Closed

Nature code after eject #554

Jiansen opened this issue Sep 2, 2016 · 1 comment

Comments

@Jiansen
Copy link
Contributor

Jiansen commented Sep 2, 2016

Following up on #257 , we could try to make eject result more natural.

For example I think it might make sense to try to write babel.dev.js and babel.prod.js without all those crazy require.resolves and then put the require.resolve mapping behind an // @remove-on-eject.

@gaearon
Copy link
Contributor

gaearon commented Sep 24, 2016

The eject output is nicer with 0.5.x and we killed Babel configs completely in favor of a preset.

@gaearon gaearon closed this as completed Sep 24, 2016
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants