Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(init): support scoped npm packages #27128

Merged
merged 1 commit into from
Nov 28, 2024
Merged

Conversation

marvinhagemeister
Copy link
Contributor

The naming scheme for create npm packages varies depending on whether they are scoped or not. We only supported unscoped packages prior to this PR. This PR adds support for all the following cases which npm supports:

See https://docs.npmjs.com/cli/v8/commands/npm-init#description

Fixes #27127

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this

@marvinhagemeister marvinhagemeister merged commit 026bbc4 into main Nov 28, 2024
17 checks passed
@marvinhagemeister marvinhagemeister deleted the npm-init-scoped branch November 28, 2024 14:07
bartlomieju pushed a commit that referenced this pull request Nov 28, 2024
The naming scheme for create npm packages varies depending on whether
they are scoped or not. We only supported unscoped packages prior to
this PR. This PR adds support for all the following cases which npm
supports:

- `foo` -> `create-foo`
- `@foo/bar` -> `@foo/create-bar`
- `@foo` -> `@foo/create`
- `@[email protected]` -> `@foo/[email protected]`
- `@foo/[email protected]` -> `@foo/[email protected]`

See https://docs.npmjs.com/cli/v8/commands/npm-init#description

Fixes #27127
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

deno init --npm doesn't support namespaced npm packages
2 participants