I'm building a webapp with webpack and having some problems I can't figure out my self or with the documentation.
What I'd like to achieve is to configure webpack as such as it doesn't include one particular json file or all of them into the main bundle. But, it should still be possible to require them as like this:
define(['app/config.json'], function (config) {
...
});
My current webpack configuration for json files looks like this:
module: {
loaders: [
{
test: /\.json/,
loader: "json"
},
// ...
]
}
The above shown configuration loads the JSON file, parses it and modules that require them simply get an instantiated js object. Marvelous! The config.json files contains some installation specific variables which should be editable by the user of the application.
When using the file-loader like this:
{
test: /\.json/,
loader: "file",
query: {
name: 'res/[name].[ext]'
}
},
the JSON file is not included in the bundle, but requiring it doesn't load the file, it simply returns the filename. Any ideas?
Code splitting is one of the most compelling features of webpack. This feature allows you to split your code into various bundles which can then be loaded on demand or in parallel.
It does so by scanning your JavaScript code from an entry point (usually the index. js file) and then following the import statements that are written in that entry point. Webpack will repeat the process until it has all the files and modules needed by your web application.
Webpack injects some code into main. js which takes care of lazy loading async chunks and stops from loading same chunks again and again. When a route changes, React router calls a Webpack function to load a chunk file and Webpack after done loading runs it, which chunk then would internally ask React to do something.
Chunk: This webpack-specific term is used internally to manage the bundling process. Bundles are composed out of chunks, of which there are several types (e.g. entry and child).
the JSON file is not included in the bundle, but requiring it doesn't load the file, it simply returns the filename. Any ideas?
That's the whole point of file-loader. This is the reason why it works so well with assets like images. It probably won't work for your use case, though, as you would have to query the file based on the returned path itself (against your idea).
If you explicitly want to separate that JSON, maybe you could use the CommonsChunkPlugin for that. This would mean you would have to implement a separate entry point that exposes the data. It could be something trivial like this:
module.exports = require('app/config.json');
You would then point at this proxy from your application. CommonsChunkPlugin would deal with your splitting requirement.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With