Fork-ts-checker-webpack-plugin: Invalid deploy key
@etienne-dldc @smonteil NPM deploy key doesn't work again - please send me a new one
piotr-oles
All 3 comments
um... this is annoying, I think we should transfer ownership of the npm package to you so this issue stop happening, @smonteil this should do : https://docs.npmjs.com/cli/owner .
etienne-dldc
on 22 Dec 2017
@smonteil Thank you for the token :) I would be thankful for transferring NPM ownership. The repository still will be on the Realytics account :)
piotr-oles
on 23 Dec 2017
I'd just like to second the desire to add @piotr-oles as an owner of fork-ts-checker-webpack-plugin. FWIW, if you're concerned about losing control, it is not necessary to transfer the publishing rights entirely. You can simply add him as another owner. See the npm docs here:
https://docs.npmjs.com/cli/owner
By way of example, ts-loader has 3 owners.
If you could add @piotr-oles as an owner it would make shipping new versions of the checker a much less difficult experience! 馃尰
johnnyreilly
on 24 Dec 2017
Related issues
JasonIsGithubbin
路
4Comments
IgnusG
路
3Comments
StefanoMagrassi
路
3Comments
TokugawaTakesi
路
4Comments
Cristy94
路
4Comments
Most helpful comment
I'd just like to second the desire to add @piotr-oles as an owner of
fork-ts-checker-webpack-plugin. FWIW, if you're concerned about losing control, it is not necessary to transfer the publishing rights entirely. You can simply add him as another owner. See the npm docs here:https://docs.npmjs.com/cli/owner
By way of example,
ts-loaderhas 3 owners.If you could add @piotr-oles as an owner it would make shipping new versions of the checker a much less difficult experience! 馃尰