Set package.json private flag to false for npm publication
Changed `"private"` to `false` in package.json to allow publishing the package to npm. The `"access": "restricted"` setting ensures that access remains limited to @soulcraft organization members. Updated README to reflect the new configuration.
This commit is contained in:
parent
7638506ffa
commit
99bc4990bd
2 changed files with 3 additions and 3 deletions
|
|
@ -135,13 +135,13 @@ To publish updates to the package:
|
|||
|
||||
Note that the package has the following configuration in package.json:
|
||||
```json
|
||||
"private": true,
|
||||
"private": false,
|
||||
"publishConfig": {
|
||||
"access": "restricted"
|
||||
}
|
||||
```
|
||||
|
||||
This ensures that the package is only accessible to users with appropriate permissions within the @soulcraft organization.
|
||||
This ensures that the package is only accessible to users with appropriate permissions within the @soulcraft organization. The `"access": "restricted"` setting limits access to the package to members of the @soulcraft organization, while `"private": false` allows the package to be published to npm.
|
||||
|
||||
### Installing the Private Package
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@
|
|||
],
|
||||
"author": "David Snelling (david@soulcraft.com)",
|
||||
"license": "MIT",
|
||||
"private": true,
|
||||
"private": false,
|
||||
"publishConfig": {
|
||||
"access": "restricted"
|
||||
},
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue