Let’s do some 101 on why you should care about webpack in the first place.
.apk file on Android or your
.ipa file on iOS.
There are two performance ramifications to this approach.
<script> tag in Safari. Much like adding a bunch of
With that background out of the way let’s return to your original questions:
Is this file being used by default? Or do you have to do something to enable it in the build process?
No, the file is not used by default. You need to install the webpack plugin and run bundled builds to leverage the file.
In general it’s only recommend that you only run these bundled builds when you’re getting ready to release to the app stores. This is because bundled builds take longer, as it takes some time for webpack to do its thing.
Does this file have to be manually maintained?
Yes, and this is kind of annoying. You can refer to the starter template on GitHub for updates, but we should think of ways we can make this easier.
Do you have to put every module you create in this file? Only some?
Why should I use this bundle-config approach? Any advantages?
For these questions I’ll defer to our experts that have a bit more webpack knowledge. The one webpack-enabled app that I maintain, Groceries doesn’t use this
bundle-config file at all, so I’m kind of curious what this file is doing as well.