feat: Add manifest functionality #48
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding ability to output to a manifest JSON file instead of directly injecting paths to a template (via:
manifest: trueconfig option) .This solves a use case where the
HtmlWebpackPluginis not being used. The manifest file can be later read by the server and it can choose how to manage them. Similar to: https://www.npmjs.com/package/webpack-assets-manifestI see that
html-webpack-pluginis listed as a peer dependency, but with this feature it would not be a required dependency. I haven't removed it from the package.json and will let you determine if it should remain a dependency or not.