Workbox: Move to npm orgs?

[jeffposnick]

Library Affected:
all

See https://docs.npmjs.com/misc/orgs

I can see the benefit of grouping all the "official" modules under @workbox.

It would also be nice to manage permissions on the organization level, rather than having to manually add all the folks who potentially might need to publish to npm to each individual package.

[addyosmani]

Drive-by thoughts:

• Are there user perceivable benefits or downsides to this change? Is switching to an org mainly for our own reasoning + permissions management needs.

• If we want to do this, we should do it for launch or a future major version change. It can get confusing for users (or has in other cases) when some of your community articles talk about npm install foo and official docs say npm install @foo/bar. I experienced this quite a bit when Angular made the shift to orgs.

[gauntface]

I'm personally not in favor of this because of the mental overhead for developers (i.e. remembering the org name followed by module name: workbox/*)

[jeffposnick]

I don't feel strongly either way—was just throwing it out there.

@gauntface's negative stance means it's worth leaving things un-organiz-ed.

[sindresorhus]

Just for reference, you can use npm orgs without using scoped packages (@workbox/*). I have for example a chalk org to ease permission maintenance, but none of the packages are scoped.

[gauntface]

@jeffposnick it's back in the game.

@sindresorhus is it relatively easy to set up / anything we should be aware of?

[addyosmani]

@sindresorhus Oh super neat. I had no idea the orgs could be used without packages themselves being. With that in mind, I'd be down with us going down that path here.

Totes aside: how did you even come across this issue? :D.

[sindresorhus]

@gauntface The only slight annoyance is that the person that originally published the npm package is the one that has to add it to the org. At least it was like that a month ago.

This is the command you use to add a package to an org:

npm access grant read-write org-name:developers package-name

[sindresorhus]

Totes aside: how did you even come across this issue? :D.

I was bored, so I stalked your recent activity.

[jeffposnick]

We're live with 12 packages owned by the @workboxjs org: https://www.npmjs.com/org/workboxjs