Skip to content
This repository was archived by the owner on Aug 20, 2018. It is now read-only.

docs(README): should we ever explicitly keep json-loader in config? #44

Closed
tom-spalding opened this issue Mar 3, 2017 · 1 comment
Closed

docs(README): should we ever explicitly keep json-loader in config? #44

tom-spalding opened this issue Mar 3, 2017 · 1 comment
Assignees
@michael-ciniawsky
Labels
type: Documentation

Comments

@tom-spalding
Copy link

I'm happy to see that json-loader works automatically in webpack 2 😸 https://webpack.js.org/guides/migrating/#json-loader-is-not-required-anymore.

When no loader has been configured for a JSON file, webpack will automatically try to load the JSON file with the json-loader.

My question though, is there any reason (besides if you have different file extensions) to explicitly write this in the config?
@michael-ciniawsky michael-ciniawsky self-assigned this Mar 13, 2017
@michael-ciniawsky michael-ciniawsky mentioned this issue Mar 13, 2017
Closed
@joshwiens joshwiens removed the question label May 1, 2017
@michael-ciniawsky michael-ciniawsky changed the title question: should we ever explicitly keep json-loader in config docs(README): should we ever explicitly keep json-loader in config? Jul 22, 2017
@michael-ciniawsky michael-ciniawsky mentioned this issue Jul 22, 2017
Merged
@tom-spalding
Copy link
Author

thanks!

@viankakrisna viankakrisna mentioned this issue Jan 9, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@michael-ciniawsky michael-ciniawsky

Labels
type: Documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tom-spalding @michael-ciniawsky @joshwiens