Upgrade to Webpack 3 #224
Merged
Upgrade to Webpack 3 #224
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjoerge
approved these changes
Oct 2, 2017
|
I'm thinking we should probably release from this branch directly in order to keep |
|
Yeah, thats probably safer 👍 |
|
Published as |
rexxars
force-pushed
the
webpack-3
branch
2 times, most recently
from
b71a8df
to
868afef
Compare
rexxars
added a commit
that referenced
this pull request
Oct 6, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 11, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 11, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 12, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades the build infrastructure to use webpack 3 and the latest version of postcss.
It also includes @bjoerge's work on upgrading storybook and makes the necessary changes for it to
work in webpack 3 context.
This is a very big change infrastructure-wise, and is not something I want to merge into next without testing it thoroughly. I suppose the logical next step would be to publish a canary build that we could test various projects with, in both a development and a build setting and see if it works as expected.
Thoughts?