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

Fix bug that causes webpack.styles=false to fail. #312

Merged
merged 1 commit into from
May 30, 2017
Merged

Fix bug that causes webpack.styles=false to fail. #312

merged 1 commit into from
May 30, 2017

Conversation

seanofw
Copy link
Contributor

@seanofw seanofw commented May 30, 2017

There's a type-testing bug in getUserConfig.js that prevents webpack.styles from being able to be set to false, like the documentation says it should be able to be. The previous if-condition correctly falls-through to the if-condition on line 495, which then incorrectly fails because the type doesn't match object.

This pull request contains a simple one-line fix for the bug. Tested locally, and it works as expected. Cheers! :-)

@insin
Copy link
Owner

insin commented May 30, 2017

Nice catch, thanks!

@insin insin merged commit 9a1be9f into insin:master May 30, 2017
@seanofw
Copy link
Contributor Author

seanofw commented May 30, 2017

I caught it 'cuz I tried using it, and it exploded. Didn't take long to find the cause, though.

I would appreciate knowing when the fix is pushed into the npm registry, so that I can update my local builds to stop using my temporarily-hacked copy of nwb.

insin added a commit that referenced this pull request May 30, 2017
@insin
Copy link
Owner

insin commented May 30, 2017

@seanofw …now :D

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

Successfully merging this pull request may close these issues.

2 participants