-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to publish unscoped packages to the GitHub Package Registry #243
Comments
To clear, you want to publish a remarkjs-scoped package to the remarkjs GPR (because GPR only allows remarkjs-scoped packages to be published to a remarkjs-owned repo) but you don't want to add the scope to the package name in package.json, right? This possible. Can you point to a specific failing package.json, . npmrc and build.yaml? By the way, why is the repository in vscode-remark pointing to a mrmlnc-owned repo? https://github.com/remarkjs/vscode-remark/blob/main/package.json#L15 |
Correct!
Cool!
Sure, I'm working on this in remarkjs/vscode-remark#40, so please poke around there.
Because it has not yet been updated after being moved from @mrmlnc. That is part of what I'm working on in remarkjs/vscode-remark#40. |
Hello everyone. Thank you for responses. GitHub Packages should be scoped. You can not publish unscoped packages to GitHub packages. You can override name of the package by this command: For now I'm going to close the issue. If you have any concerns feel free to ping us. |
Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 4.28.3 to 4.28.4. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v4.28.4/packages/eslint-plugin) --- updated-dependencies: - dependency-name: "@typescript-eslint/eslint-plugin" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
As requested in #73 (comment), this issue is an attempt to explain how I'm unable to get
setup-node
to help me publish an unscoped NPM package to the GitHub Package Registry. Thename
of the package isvscode-remark
(notice the lack of scope).Here's the relevant job from my workflow:
The
npm publish
step in the above workflow fails with the following error:I've also tried to create an
.npmrc
file manually, like so:And by committing the following
.npmrc
file to Git:(The contents, including
always-auth=false
, is mostly identical to the contents of.npmrc
aftersetup-node
has executed). I've also tried addingpublishConfig
to mypackage.json
:However, all of these attempts fail with the following error:
If it's possible to publish an unscoped package to the GitHub Package Registry without modifying its
name
, by adding the scope through some other means only when publishing to GPR (but not to NPM), clear guidance to how that is accomplished would be highly appreciated.Even better would be if
setup-node
was modified to take care of this or if there was annpm-publish
action that took care of this automatically. The hacks seen outlined in #73 and #53 to "fix" this are rather bad, imho.The text was updated successfully, but these errors were encountered: