You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where bundles are output to more than one directory, bundle paths are incorrect.
I'm using webpack-bundle-analyser with Gatsby via gatsby-plugin-webpack-bundle-analyser-v2 which is a very thin plugin. Gatsby adds bundles to /public/, however another plugin I use gatsby-plugin-netlify-cms adds bundles to /public/admin/. When BundleAnalyzerPluginderives the bundleDir it resolves (using this.compiler.outputPath to /path/to/public/admin/ which it then uses as a prefix for all bundle paths. This means only the bundles that are generated to /admin/ are correct. The rest are not and result in warnings:
Error parsing bundle asset "/Users/me/Sites/www/public/app.js": no such file
It seems the current architecture can't handle situations where bundles are in written to different locations.
Issue description
Where bundles are output to more than one directory, bundle paths are incorrect.
I'm using
webpack-bundle-analyser
with Gatsby via gatsby-plugin-webpack-bundle-analyser-v2 which is a very thin plugin. Gatsby adds bundles to/public/
, however another plugin I use gatsby-plugin-netlify-cms adds bundles to/public/admin/
. WhenBundleAnalyzerPlugin
derives thebundleDir
it resolves (usingthis.compiler.outputPath
to/path/to/public/admin/
which it then uses as a prefix for all bundle paths. This means only the bundles that are generated to/admin/
are correct. The rest are not and result in warnings:It seems the current architecture can't handle situations where bundles are in written to different locations.
Technical info
The text was updated successfully, but these errors were encountered: