-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Release new @oxc-project/types
NPM package
#6862
Labels
C-bug
Category - Bug
Comments
|
overlookmotel
pushed a commit
that referenced
this issue
Oct 24, 2024
Closes #6862. Possible options: - `oxc-types` - `@oxc-project/types` - `@oxc-ast/types` - `oxc-ast-types`
Looks like the release CI needs to be kickstarted by a manual release with how the version check works. |
overlookmotel
changed the title
Fix NPM package name for AST types
Release new Oct 25, 2024
@oxc-project/types
NPM package
Orenbek
pushed a commit
to Orenbek/oxc
that referenced
this issue
Oct 28, 2024
Closes oxc-project#6862. Possible options: - `oxc-types` - `@oxc-project/types` - `@oxc-ast/types` - `oxc-ast-types`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#6755 and #6796 introduced a new NPM package
@oxc/types
. But we don't control the@oxc
NPM scope. We need to decide a name for this package.oxc-types
?@oxc-project/types
?Also, those PRs altered the publish workflows, and I'm not sure if this was all reviewed or not before merging.
We should not make a release until this is resolved. Releasing from current state of repo would break
oxc-parser
and@oxc-parser/wasm
NPM packages.The text was updated successfully, but these errors were encountered: