Grant npm read-write access to sweetalert2 collaborators

Currently, there are 5 SweetAlert2 collaborators:

npm access ls-collaborators sweetalert2
{
  "toverux": "read-write",
  "samturrell": "read-write",
  "acupajoe": "read-write",
  "zen_flow": "read-write",
  "limonte": "read-write"
}

That will ensure that if bus-factor will happen to @limonte, sweetalert2 might still be maintained by the rest of the collaborators.

On the other hand,

npm access ls-collaborators @toverux/ngx-sweetalert2
{
  "toverux": "read-write"
}

So, if something will happen to @toverux, the project (or at least npm package name) will be ☠️

---

Is it okay for you @toverux to align the list of collaborators with the one from sweetalert2? As I understand correctly, it could be done by running:

npm access grant read-write sweetalert2 

from the ngx-sweetalert2 directory.

[limonte]

@toverux I guess you need to follow the workaround suggestion by Lars Willighagen.

Waiting for https://github.com/npm/cli/pull/2 to be merged could take quite a while 😃

That PR btw shows the terrible state of the npm/cli future.

• 1 developer
• 1 PR
• 377 changed files
• 26,824 changed LoC
• no code review
• no discussion

With such workflow, it’s impossible to build a reliable software. Long live, Yarn.

[toverux]

Oh that is a strange choice. I don’t know what they were missing in Github’s issues… anyway, here we go: https://npm.community/t/npm-access-grant-team-is-required-and-must-be-of-type-string/2641