Repository navigation
docs: use scoped package name in npx commands - #44
Merged
kamilmysliwiec merged 2 commits intoOct 22, 2026
Merged
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
JSDoc of
migrateoption on both stores andWebhookSchemaErrorexample saynpx nest-webhooks migrate, while docs move tonpx @nestjs/webhooks migratein nestjs/docs.nestjs.com#3646. Tests assert old kit text since lockfile has@nestjs/store-kit0.1.0What is the new behavior?
Follow up to nestjs/store-kit#36 (released in kit 0.1.1), CLI and store print
npx @nestjs/webhooks ...there instead ofnest-webhooks .... Here it's two commits:npx @nestjs/webhooks migrate@nestjs/store-kit0.1.1, assertions on kit text intests/postgres/cli.spec.tsand bothmigrations.spec.tsfollow it (6 lines)Package has single bin so npx runs
nest-webhooksfrom it, and with scoped name it always resolves to official package. Bin itself stays, becuase scripts may callnest-webhooksdirectlyDoes this PR introduce a breaking change?
Other information
Build, lint, tsc and full suite pass locally against PostgreSQL 18.6 and MySQL 8.4