fix: export webpack helper subpath#61
Open
xianzuyang9-blip wants to merge 1 commit into
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.
Fixes #60.
What changed
vortex-api/bin/webpack.vortex-api/bin/webpack.jssubpath for consumers that include the extension.The helper is already included in the npm package via
files: ["./bin", ...]and the migration guide still documents the webpack helper path, but the v2 export map only exposed the root typing entrypoint. That makes Node reject existing webpack configs withERR_PACKAGE_PATH_NOT_EXPORTED.Validation
Before this change, this fails with
ERR_PACKAGE_PATH_NOT_EXPORTED:node -e "require.resolve('vortex-api/bin/webpack', { paths: [process.cwd()] })"After this change, these pass: