-
Notifications
You must be signed in to change notification settings - Fork 82
Add support for webpack2 #33
Comments
I'm using json-loader with webpack v2 and it's working for me. Do you use |
Yep,
|
@monolithed have you found a workaround for this yet? Let me know if I can help in any way! |
@SpaceK33z seems like removing the requirement for |
@waltfy it might be related to webpack-contrib/extract-text-webpack-plugin#265, but not sure. |
Have you tried to delete your
I rolled to a previous version 😄 |
Jep, just tried it again. What version of which package did you rollback to? And does the problem disappear if you don't use extract-text-webpack-plugin? |
@SpaceK33z, I meant |
Okay, but could you checkout if it happens without extract-text-webpack-plugin? This is crucial for me to know because if so, it is probably an issue with extract-text-webpack-plugin. |
Alas, I did not keep that state in the history of commits, sorry. |
I'm going to close this since webpack v2 with json-loader does work, but it is some other package (probably extract-text-webpack-plugin since that fixed it for @waltfy) that introduces this bug. |
@SpaceK33z @monolithed I think it makes sense to close the issue. I'll post any useful information I find here, it'll maybe help other people. Thanks! 👍 |
I'm getting the following error when loading json files with Webpack 2 and this plugin (which I don't have with Webpack 1.x:
Any ideas? I guess the 'm' in error is part of "module.exports" or something like that. |
I'm getting the exact same as @dsebastien. |
I've got the same error:
I'm using node in version 4.6.0 |
Okay I'll reopen this, but please provide some useful information so we can narrow this down. Try to remove as many plugins / loaders as possible. Especially try if removing |
I changed my webpack.config config a bit and now it is working again. In the webpack.config I'm now using:
and in my files instead of importing the files like this before:
I had to remove the json! at the beginning of the path like
now it is working in node as well as in the browser environment |
@crebuh see webpack/webpack#3359 for a plan on how we want to avoid the issue you had from happening again. Closing this again since you can fix that error with the above fix. |
In my case, I've doubled checked but I didn't specify the "json!" in the require call, so normally I'm only using the loader once... |
webpack@^2.1.0-beta.25
The text was updated successfully, but these errors were encountered: