Skip to content
This repository was archived by the owner on May 16, 2024. It is now read-only.

Merge in latest from mipearson/webpack-rails #2

Merged
merged 27 commits into from
Jul 12, 2017
Merged

Conversation

shirish-pampoorickal
Copy link
Member

The main fork has been upgraded to v0.9.10 whereas we are still on v0.9.8. This PR takes care of it

Zinssmeister and others added 27 commits August 1, 2016 15:25
This allows webpack-rails to be used with non-breaking errors (such as linting).
Only error if manifest error was a module build failure
Prior to this change, webpack-dev-server would also be enabled in
environments like staging, which is not something one would expect.

This seems like a more sensible default.
Only enable dev server in development & test
Use existing NODE_ENV if available
Fixes SSL certificate verification
@shirish-pampoorickal shirish-pampoorickal self-assigned this Jul 11, 2017
@juanca
Copy link

juanca commented Jul 12, 2017

Thanks! Mergin.

@juanca juanca merged commit dc616af into master Jul 12, 2017
@juanca juanca deleted the update_to_v0.9.10 branch July 12, 2017 00:12
@naganowl
Copy link

@shirish-pampoorickal do we have a branch that tests that this works for us?

@shirish-pampoorickal
Copy link
Member Author

Yes, on bigmaven its rails_42_on_latest_webpack

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

9 participants