This repository has been archived by the owner on Jun 25, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 59
Loading JSON files with bundle-loader crashes #74
Comments
If anyone else is encountering the same bug, my current workaround is to go back to using to module: {
rules: [{
test: /\.json$/i,
type: 'javascript/auto',
loader: 'json-loader',
}],
}, Sadly I haven't found a way to do that for |
I think this is related to webpack/webpack#6572, as applying webpack/webpack#6572 (comment) fixes the issue. |
This was referenced Apr 16, 2018
Adding the following code snippet just before return result.join(""); resolves the issue but it is not nice. I don't know how to property get the generator and parser instance:
Is there a better api to get the instance other then searching in the other modules? |
rmja
added a commit
to rmja/bundle-loader
that referenced
this issue
Jul 4, 2018
This is a proposal for a fix to webpack-contrib#74. It is not elegant but it gets the job done
rmja
added a commit
to rmja/bundle-loader
that referenced
this issue
Jul 4, 2018
This is a proposal for a fix to webpack-contrib#74. It is not elegant but it gets the job done
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I'm not sure what I'm doing wrong but for some reason, if I try to lazily load JSON files using this loader, webpack interprets the generated loading code as if it were JSON too and tries to parse it.
This happens using Webpack 4.1.1
I assume it's because the name of the resource bundle-loader generates ends with
.json
too. (eg../node_modules/bundle-loader?lazy&name=file-[name]!./json-files/a.json
)I reproduced the issue using only bundle-loader and a couple of JSON files here: http://github.com/Ephys/bundle-loader-bug
Here is the webpack log of the above project: https://github.com/Ephys/bundle-loader-bug/blob/master/stacktrace.log
Thank you in advance for your help! :)
The text was updated successfully, but these errors were encountered: