Maintenance is frozen

[kentcdodds]

I'm no longer watching this repo. This babel plugin is pretty much done and I'm no longer using it much. If you really need something changed, then I suggest you fork it.

Unfortunately, this plugin is so widely used that it would be irresponsible for me to hand over publish rights to someone I don't know and trust. So I'm basically freezing development unless someone who fits that description wants to take it over.

I might be willing to accept a PR to keep this project up-to-date for compatibility reasons with babel. But in general, there's no more maintenance that will happen on this package. Thanks for understanding.

[conartist6]

Thanks for letting people know! I've watched so many repos where support quietly disappears leaving open source contributors wondering what is going on.

I would consider taking over maintainership, though it would obviously be up to Kent as to whether he would trust me with that role. I've helped out here occasionally, though most of my work thus far has been on iter-tools (283 commits) and macrome.

[kentcdodds]

I was thinking of all people you would be the most likely to hand over ownership to. I think it would probably be ok. The event-stream incident just has me a little paranoid 😬

Just ping me when there's a PR needing my attention, but really I think we're mostly done anyway so 🤷‍♂️

[conartist6]

@kentcdodds are you willing to revisit publish rights again? Then we could put this issue to bed. I've been a full time professional (self-paid) OSS developer for the last two years now, and have been focusing my energy on building the next babel.

[kentcdodds]

Agreed. I'm happy to give you publish rights @conartist6 👍 What's your npm username? I'll remove my own token, then give you publish access and you can have full control over this project. Let me know what else you'll need.

[conartist6]

Alright! I'm conartist6 there too.

[kentcdodds]

Interesting. I can't figure out how to give you access to publish the package. They changed the UI and the commands aren't working either 😭

Here's everything I tried:

Last login: Thu May 25 05:02:41 on ttys013
~ 🎊
$ npm whoami
kentcdodds
~ 🎊
$ npm access grant read-write conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! Second argument used incorrect format.
npm ERR! Example: @example:developers
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_08_57_200Z-debug-0.log
~ 🎊
$ npm access ls-contributors babel-plugin-macros conartist6
npm ERR! code EUSAGE
npm ERR! 
npm ERR! ls-contributors is not a recognized subcommand.
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_09_15_935Z-debug-0.log
~ 🎊
$ npm access ls-collaborators babel-plugin-macros conartist6
npm WARN access ls-collaborators subcommand will be removed in the next version of npm
{
  "kentcdodds": "read-write"
}
~ 🎊
$ npm access grant read-write @conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! Second argument used incorrect format.
npm ERR! Example: @example:developers
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_09_43_790Z-debug-0.log
~ 🎊
$ npm access grant write <conartist6> babel-plugin-macros
zsh: no such file or directory: conartist6
~ 🎊
$ npm access grant write conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! First argument must be either `read-only` or `read-write`.
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_10_36_228Z-debug-0.log
~ 🎊
$ npm access grant read-write conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! Second argument used incorrect format.
npm ERR! Example: @example:developers
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_10_44_038Z-debug-0.log
~ 🎊
$ npm access grant write conartist6 babel-plugin-macros 
npm ERR! code EUSAGE
npm ERR! 
npm ERR! First argument must be either `read-only` or `read-write`.
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_10_58_697Z-debug-0.log
~ 🎊
$ npm access edit babel-plugin-macros
npm ERR! edit subcommand is not implemented

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_28_33_100Z-debug-0.log
~ 🎊
$ npm access grant write conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! First argument must be either `read-only` or `read-write`.
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_29_39_930Z-debug-0.log
~ 🎊
$ npm access grant read-write conartist6 babel-plugin-macros
npm ERR! code EUSAGE
npm ERR! 
npm ERR! Second argument used incorrect format.
npm ERR! Example: @example:developers
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_30_16_330Z-debug-0.log
~ 🎊
$ npm access grant read-write babel-plugin-macros conartist6
npm ERR! code EUSAGE
npm ERR! 
npm ERR! Second argument used incorrect format.
npm ERR! Example: @example:developers
npm ERR! 
npm ERR! Set access level on published packages
npm ERR! 
npm ERR! Usage:
npm ERR! npm access public [<package>]
npm ERR! npm access restricted [<package>]
npm ERR! npm access grant <read-only|read-write> <scope:team> [<package>]
npm ERR! npm access revoke <scope:team> [<package>]
npm ERR! npm access 2fa-required [<package>]
npm ERR! npm access 2fa-not-required [<package>]
npm ERR! npm access ls-packages [<user>|<scope>|<scope:team>]
npm ERR! npm access ls-collaborators [<package> [<user>]]
npm ERR! npm access edit [<package>]
npm ERR! 
npm ERR! Options:
npm ERR! [--registry <registry>] [--otp <otp>]
npm ERR! 
npm ERR! Run "npm help access" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kentcdodds/.npm/_logs/2023-05-30T21_31_04_297Z-debug-0.log
~ 🎊
$ 

😩

[conartist6]

According to what you pasted the syntax is

npm access grant <read-only|read-write> <scope:team> [<package>]

I notice other places <user> is listed as potential alternative to <scope:team>, but not for grant.

[kentcdodds]

Yeah, so that's a bummer... I don't have any idea how to give you access. The npm website used to have a UI for this, but it doesn't appear to anymore 😬

[conartist6]

Don't worry I'll figure it out. Since I'm the maintainer it should go into my TODO list not yours, it's just that at the moment there's no urgency to this so I have higher priorities.

[kentcdodds]

Sounds good. Just FYI, I've already deleted my npm token from this repo's secrets, so until we figure this out, it won't be able to have a release.