Post-es2015 webpack #4
Open
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
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 is a follow-on to the previous PR to bring in ES2015 support (hence all the commits before the squashed last-commit that is the subject of this one). If you do merge the es2015, then I can rebase and this will be a single commit.
This removes the gulp + Browserify in favor of npm + webpack.
I'm not sure it's ready for a merge, but wanted to have it here in case someone wanted to have a small example of doing server-side-rendering with webpack.
I'd like to go through and make sure that they are 100% overlapping in features - at the moment, all the autoprefixer + sass transformation is there, but have to double-check the rest.
You can get started with a simple
npm start; the rest is documented by runningnpm run- you'll get a list of other commands.Toodles!