[foob]

Amusingly, they deprecated it with a message of "Unpublished" instead of actually unpublishing it [1]. When you use npm unpublish it removes the package version from the registry, when you use npm deprecate it leaves it there and simply marks the package as deprecated with your message. I have to imagine the point was to make it harder for people to download the source map, so to deprecate it with this message gives off a bit of claude, unpublish the latest version of this package for me vibe.

[1] - https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2....

[therealpygon]

Commit Message: undo undo unpublish ctrl-z ctrl-c No, stop, don’t commit tha

[dolmen]

Esc :q!

[hanspagel]

You can’t unpublish a npm package with more than 100 downloads I think.

[Normal_gaussian]

The policy is https://docs.npmjs.com/policies/unpublish

    Packages published less than 72 hours ago
    
    For newly created packages, as long as no other packages in the npm Public Registry depend on your package, you can unpublish anytime within the first 72 hours after publishing.

There are 231+ packages that depend on this one, and I imagine they mostly use permissive enough version ranges that this was included.

[firloop]

Looks like Anthropic called in a favor and it's removed now.

[SV_BubbleTime]

Ah, another you can’t, but they can.

I’m still a little humored over peak web3 and the DAO / soft contract nonsense. Like in order to stop fraud entire coins were forked…

[inglor]

Sure you can, if you have a legitimate case you can ask npm to unpublish and they handle things manually :)

[kevstev]

I have had to do this, well over a decade ago now, when working at a place that was a pretty big deal in the node world, and node was still pretty new. They helped us.

I would imagine GH would do the same if its a high enough profile issue.

[jamietanna]

Yep, we had to do this recently with Renovate, where we had too many releases, and new publishing hit a size limit on the registry, so we needed support to help us unpublish a load of old releases

[Breza]

The novel Red Team Blues involves a similar plot with a crypto token that's supposed to be immutable. It's pretty entertaining.

[jacquesm]

Good luck with that.

[scotty79]

I think they are aware that things don't disappear from the internet. So they chose just to gently indicate that it wasn't meant for publishing.

[jaapz]

You can say what you want about anthropic but they sure as hell are dogfooding the crap out of claude code lmao

[kami23]

In all my years of writing tools for other devs, dog fooding is the really the best way to develop IMO. The annoying bugs get squashed out because I get frustrated with it in my flow.

Iterating on a MCP tool while having Claude try to use it has been a really great way of getting it to work how others are going to use it coming in blind.

Yes it's buggy as hell, but as someone echoed earlier if the tool works most of the time, a lot of people don't care. Moving fast and breaking things is the way in an arms race.

[danudey]

> In all my years of writing tools for other devs

Not just tools for devs, this is true in a lot of cases.

I used to work at Fortinet and every now and then we'd get an e-mail from information services letting us know that they would be installing a dev build of FortiOS on our internal (production) corporate network.

In cases where we needed more debug logging from a feature or where we had a fix we had to test on a live network, and if we didn't want to ship a test firmware to some huge client and say 'here, see if this bricks your network or not', they would hand it off to our IT team and we'd install it on our own network to run. After all, if you're not confident enough to run it how can you be confident enough to ask your customers to run it?

Now if they could just get the hang of not hard-coding admin credentials into the software they'd have a lot to brag about!