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.
Description of changes
There was an issue in the repository that made this sequence fail, when cloning the repo for the first time:
pnpm install
->pnpm build
->cd debug && pnpm dev
Because the
dist/bin.js
file was only generated after thepnpm build
step, it wasn't installed in the debug project during the initialpnpm install
step. This forced developers working on this project to runpnpm install
twice, once before the build, and again after the build.This change adds a
/bin/create-schemas.js
file which always exists and removes the need to runpnpm install
twice.Boyscout
Renamed the
/src/bin.ts
file to/src/cli.ts
, since it is the entrypoint of the CLI.Also add the
"files"
field to thepackage.json
. I noticed our/test
and/src
folders got included in the published package. This isn't bad per-se, but we are installing more files than we need to on our user's filesystem, which is rude.Breaking changes
N/A
Additional checks
N/A