Skip to content
This repository has been archived by the owner on Sep 11, 2018. It is now read-only.

fix: correctly define NODE_ENV for production #42

Merged
merged 1 commit into from
Jun 27, 2018
Merged

fix: correctly define NODE_ENV for production #42

merged 1 commit into from
Jun 27, 2018

Conversation

vitalyster
Copy link
Contributor

@vitalyster vitalyster commented Jun 27, 2018

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

Fixes #41

Breaking Changes

None

Additional Info

None

@jsf-clabot
Copy link

jsf-clabot commented Jun 27, 2018

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@shellscape shellscape left a comment

Choose a reason for hiding this comment

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

Thanks for the PR 🍺

Please run npm run test -- --u on your end, and commit the updated snapshot files. Then the CI tests will pass. (It's always good practice to run npm run lint and npm run test before creating a PR)

@vitalyster
Copy link
Contributor Author

👍 It also requires me to fix commit message, but now fails CI itself, please restart

@shellscape shellscape merged commit 016d4a9 into webpack-contrib:master Jun 27, 2018
@shellscape shellscape changed the title Correctly define NODE_ENV when running production build fix: correctly define NODE_ENV for production Jun 27, 2018
@vitalyster vitalyster deleted the patch-1 branch June 28, 2018 06:11
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.

webpack output contains duplicated dependencies after upgrading to 0.3.0
3 participants