Publish a free npm package?

Question

Is it correct that publishing a regional package npm ( @foo/bar), even as it is --access=public, is not free?

This results in an error Failed PUT 404(or 402). Is it because you need an (paid) npm organization @foo?

Update (March17): Npm organizations are now free

Answer 1

Yes, because to publish a module with a scope @fooyou need an organization with a name @foo. Thus, an area is defined by the creation of an organization with the same name, and the organizations themselves are not free.

Basically the rules:

• , .
• , .

Answer 2

, npm 'foo'.