Skip to content

Maintain the example along with the paths #1761

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

Maintain the example along with the paths #1761

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...ing-packages-to-the-registry/creating-and-publishing-scoped-public-packages.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ For less sensitive information, such as testing data, use a `.npmignore` or `.gi
To reduce the chances of publishing bugs, we recommend testing your package before publishing it to the npm registry. To test your package, run `npm install` with the full path to your package directory:

```
npm install my-package
npm install /path/to/my-test-package
```

## Publishing scoped public packages
Expand All @@ -80,7 +80,7 @@ By default, scoped packages are published with private visibility. To publish a
1. On the command line, navigate to the root directory of your package.

```
cd /path/to/package
cd /path/to/my-test-package
```

2. To publish your scoped public package to the npm registry, run:
Expand Down