Maintain the example along with the paths (#1761)
<!-- What / Why --> ### Why? The current examples are clear, it could be helpful to maintain a constant name for the paths to the hypothetical package, on any of the installation and directory navigation examples. ### Description <!-- Describe the request in detail. What it does and why it's being changed. --> Simple suggestion for changing command line examples in the **Test your package** and **Publishing your scoped public packages**
Aloof committed
Nov 3, 2025 at 21:37 UTC
ecbe2dbc506edaf5fc4b7e6f06caf972a314d86e
1 file changed
+2
-2
content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-scoped-public-packages.mdx
+2
-2
@@ -70,7 +70,7 @@ For less sensitive information, such as testing data, use a `.npmignore` or `.gi
70
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:
71
72
```
73
-npm install my-package
73
+npm install /path/to/my-test-package
74
```
75
76
## Publishing scoped public packages
@@ -80,7 +80,7 @@ By default, scoped packages are published with private visibility. To publish a
80
1. On the command line, navigate to the root directory of your package.
81
82
```
83
- cd /path/to/package
83
+ cd /path/to/my-test-package
84
```
85
86
2. To publish your scoped public package to the npm registry, run: