-
Notifications
You must be signed in to change notification settings - Fork 82
Do not try to parse again the string if it's already parsed #11
Conversation
Please merge! @sokra |
so we can use module.exports to solve this problem ?@MartinMuzatko |
AFAIK, the json-loader should just require JSON files. |
yeah, I know what you mean, I had meet this problem too. |
A proper specification for what use cases the JSON-loader really is for would be great. AFAIK the point of the JSON Loader is to require JSON Files without needing to do a |
I too came across this error. I managed to fix it with this patch (fix is the wrong word, prove that the library is broken is more appropriate). I'm also left wondering why it wasn't merged in or at least explained? |
+1 |
I think it's not merged because it's a workaround, as explained by @MartinMuzatko. A fix should be applied either in the calling library (which parses JSON twice) or in the libraries using The thing is, libraries should just have a |
Guys, I want to use { test: /\.json$/, loader: 'json-loader' },
{ test: /\.json$/, loader: 'file?name=data/[path][name].[ext]' }, How to be? |
@bora89 you should open that as a new issue, otherwise you won't get any attention on a close issue. |
Fixes #10