-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose build manifest #600
Comments
Could we utilize something like this: https://www.npmjs.com/package/webpack-manifest-plugin? |
Yep, something like this. |
Should we just use webpack-manifest-plugin on |
@lukyth Sounds reasonable. |
I use danethurber/webpack-manifest-plugin on Webpack production configuration to create a file named `asset-manifest.json` which contain a mapping of all asset filenames to their corresponding output file. `asset-manifest.json` will be located at the root of output folder. This'll resolve facebook#600
* Create asset filenames mapping on the build output I use danethurber/webpack-manifest-plugin on Webpack production configuration to create a file named `asset-manifest.json` which contain a mapping of all asset filenames to their corresponding output file. `asset-manifest.json` will be located at the root of output folder. This'll resolve #600 * Add an explanation for ManifestPlugin * Make webpack-manifest-plugin's version exact
* Create asset filenames mapping on the build output I use danethurber/webpack-manifest-plugin on Webpack production configuration to create a file named `asset-manifest.json` which contain a mapping of all asset filenames to their corresponding output file. `asset-manifest.json` will be located at the root of output folder. This'll resolve facebook#600 * Add an explanation for ManifestPlugin * Make webpack-manifest-plugin's version exact
* Create asset filenames mapping on the build output I use danethurber/webpack-manifest-plugin on Webpack production configuration to create a file named `asset-manifest.json` which contain a mapping of all asset filenames to their corresponding output file. `asset-manifest.json` will be located at the root of output folder. This'll resolve facebook#600 * Add an explanation for ManifestPlugin * Make webpack-manifest-plugin's version exact
Well done! |
We should include an additional file as the build output. This file should contain a mapping of asset file names so that tools can pick it up without having to parse index.html. This is useful for integrations like this: http://myappincome.co.uk/how-to-make-a-react-js-wordpress-plugin/.
AFAIK Webpack already provides access to such object via its API, we just need to figure out how to write it to a file, and decide on the filename.
The text was updated successfully, but these errors were encountered: