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.

Sign up for GitHub

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

Jump to bottom

[BREAKING] Use babel-preset-env instead of babel-preset-latest #54

Closed
denysdovhan opened this issue Mar 11, 2017 · 5 comments
Closed

[BREAKING] Use babel-preset-env instead of babel-preset-latest #54

denysdovhan opened this issue Mar 11, 2017 · 5 comments

Comments

@denysdovhan
Copy link
Contributor

From Babel's Slack:

image
@paulmillr
Copy link
Contributor

Not compatible with uglify-js.

@paulmillr paulmillr changed the title Use babel-preset-env instead of babel-preset-latest [BREAKING] Use babel-preset-env instead of babel-preset-latest Mar 11, 2017
@shvaikalesh
Copy link
Contributor

shvaikalesh commented Mar 12, 2017 •
edited
Loading

Detect uglifyjs-brunch and set "uglify" as target. Easy and not BREAKING.
babel/babel-preset-env#178

@shvaikalesh shvaikalesh mentioned this issue Mar 12, 2017
Merged
@denysdovhan
Copy link
Contributor Author

@shvaikalesh looks good. Seems like a possible solution.

@denysdovhan denysdovhan mentioned this issue Mar 16, 2017
Closed
@yavorsky
Copy link
Member

Yes, just add uglify: true for production.

@denysdovhan
Copy link
Contributor Author

Should be fixed by #53.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@paulmillr @yavorsky @denysdovhan @shvaikalesh