after publishing package shows up in my profile listings but itself is 404 @brinkdevteam/derive-npmignore

[binki]

At https://www.npmjs.com/org/brinkdevteam I can see a link to https://www.npmjs.com/package/@brinkdevteam/derive-npmignore but if I follow that link, I get a 404. Also,

ohnobinki@gibby ~ $ npm view @brinkdevteam/derive-npmignore
npm ERR! code E404
npm ERR! 404 Not found : @brinkdevteam/derive-npmignore
npm ERR! 404
npm ERR! 404  '@brinkdevteam/derive-npmignore' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ohnobinki/.npm/_logs/2018-08-07T03_15_10_253Z-debug.log

If I try to publish again as that error tells me to, it says I mayn’t overwrite an existing package:

ohnobinki@gibby ~/repos/@brinkdevteam/derive-npmignore $ npm publish

> @brinkdevteam/derive-npmignore@1.0.0 prepare .
> tsc -d && node ./bin/derive-npmignore.js

npm ERR! publish Failed PUT 403
npm ERR! code E403
npm ERR! You cannot publish over the previously published versions: 1.0.0. : @brinkdevteam/derive-npmignore

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ohnobinki/.npm/_logs/2018-08-07T03_15_33_921Z-debug.log

I already received the email from npmjs which tells me that the package successfully published:

Hi binki!

A new version of the package @brinkdevteam/derive-npmignore (1.0.0) was published at 2018-08-07T03:01:10.400Z from
«redacted». The shasum of this package was cf39069e4324f1a0457b1f5d41ec902a1c14ccbd.

If you have questions or security concerns, you can reply to this message or
email support@npmjs.com.

npm loves you.

Thanks in advance for any help!

[fengmk2]

Same problem to me https://github.com/npm/registry/issues/379

[binki]

@fengmk2 Looks like it to me. I saw your issue but thought I would open one myself. There’s a small chance there’s a different underlying cause—we can’t tell as npmjs outsiders.

[binki]

OK, definitely a dup of #379.