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

Format file names with backticks in working-with-the-npm-registry#publishing-a-package-using-a-local-npmrc-file #35762

Open
1 task done
nguyenalex836 opened this issue Dec 24, 2024 · 0 comments
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers packages This issue or pull request should be reviewed by the docs packages team

Comments

@nguyenalex836
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#publishing-a-package-using-a-local-npmrc-file

This issue is intended for newcomers to the OS Docs repo! 💛

If you are veteran of the OS Docs repo and are looking for issues to work on, take a look at our help wanted section

What part(s) of the article would you like to see updated?

You can use an .npmrc file to configure the scope mapping for your project. In the .npmrc file, use the GitHub Packages URL and account owner so GitHub Packages knows where to route package requests. Using an .npmrc file prevents other developers from accidentally publishing the package to npmjs.org instead of GitHub Packages.

Add the .npmrc file to the repository where GitHub Packages can find your project.

Verify the repository field in your project's package.json.

Format references to files names with backticks per our style guide

Additional information

No response

@nguyenalex836 nguyenalex836 added good first issue Good for newcomers content This issue or pull request belongs to the Docs Content team packages This issue or pull request should be reviewed by the docs packages team labels Dec 24, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Dec 24, 2024
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers packages This issue or pull request should be reviewed by the docs packages team
Projects
None yet
Development

No branches or pull requests

1 participant