Add prepare hook to run build when installed as git dependency directly #467
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.
Issue
Currently, adding chess.js as a dependency from npm works without issue, i.e.
npm install chess.js
. However, adding it as a git or Github dependency directly usingnpm install github:jhlywa/chess.js
(or similar) will cause an import error.Installing the dependency from a git repo directly is required to use commits after the most recent npm published version.
Cause
For example, Vite may give:
Failed to resolve entry for package "chess.js". The package may have incorrect main/module/exports specified in its package.json.
This occurs because the chess.js
package.json
specifies paths in thedist
directory that doesn't exist untilnpm run build
is done.Solution
This PR adds a
prepare
hook that triggersnpm run build
in the following cases:See: npm CLI life cycle scripts documentation.
This is a tiny change to
package.json
.