From bf51594f9d93607e49124c450360d99e3f878176 Mon Sep 17 00:00:00 2001 From: Josh Thomas Date: Sun, 10 Apr 2016 16:00:51 -0500 Subject: [PATCH] Update 08-publish.js to ensure publish modules are public. --- problems/08-publish.js | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/problems/08-publish.js b/problems/08-publish.js index e90ed63..74119be 100644 --- a/problems/08-publish.js +++ b/problems/08-publish.js @@ -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