Skip to content

Update 08-publish.js to ensure publish modules are public. #63

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

Closed
wants to merge 1 commit into from
Closed

Update 08-publish.js to ensure publish modules are public. #63

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
6 changes: 4 additions & 2 deletions problems/08-publish.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,11 @@ Not very good.
Luckily, that is not a problem for npm, because it's very easy for all
npm users to publish their modules and share them with the world.

Packages get into the registry by using the `npm publish` command.
Packages get into the registry by using the `npm publish --access=public` command.

Try it now. There's not much too it.
Try it now. There's not much too it. By default scoped modules are private.
The '--access=public' flag is needed to ensure scoped modules are public. This
option will remain set for all subsequent publishes.

(Make sure you're still in the right project directory, though. If you
publish something by mistake, you can remove it, but there's no guarantee
Expand Down