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

Webpack 2 #449

Merged
merged 8 commits into from
Dec 28, 2016
Merged

Webpack 2 #449

merged 8 commits into from
Dec 28, 2016

Conversation

nkzawa
Copy link
Contributor

@nkzawa nkzawa commented Dec 21, 2016

This PR upgrades webpack to v2.

btw It looks our blocker (webpack/watchpack#33) is going to be published soon.

https://github.com/webpack/watchpack/releases/tag/v1.1.2 (not released to npm yet)

It seems the tag was removed. I don't know the current status of it.

@nkzawa nkzawa mentioned this pull request Dec 21, 2016
@coveralls
Copy link

coveralls commented Dec 21, 2016

Coverage Status

Coverage increased (+2.5%) to 60.668% when pulling 4a9fbfd on webpack2 into 8c54820 on master.

'babelrc': false,
'presets': [
loader: 'babel-loader',
options: {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here we could decorate this with options.babel() to make it easier to config babel for next?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate options.babel() ?

@nkzawa
Copy link
Contributor Author

nkzawa commented Dec 28, 2016

It seems this is a blocker for v2 release. I will add the monkey-patch if needed.

@arunoda
Copy link
Contributor

arunoda commented Dec 28, 2016

Yep. That's seems like the best way to do it.

@nkzawa
Copy link
Contributor Author

nkzawa commented Dec 28, 2016

fce9f02 is the monkeypatch

@rauchg rauchg merged commit ff117b7 into master Dec 28, 2016
@rauchg rauchg deleted the webpack2 branch December 28, 2016 18:16
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 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

Successfully merging this pull request may close these issues.

4 participants