After attempting to add a tag containing a forward slash, the website stops showing package updates

[jessitron]

I tried to add a tag with a slash in it, and it didn't work, which was fine. The weird thing is, after I did that, and then published again or added more tags without slashes, the web page does not update. npm view shows the latest tags and versions, but the web page is frozen where it was before I tried to add the invalid tag.

Link to the page

https://www.npmjs.com/package/play-ts-package

(contrast the contents of versions there with npm view play-ts-package)

Logged in or logged out?

out

Expected behavior

should show the existence of 1.2.0, which shows up in npm view play-ts-package

Actual behavior

is stuck on 1.1.0

Steps to reproduce the problem

1. make a package, publish it.
2. try to add a tag with a slash in it:

   
   $ npm dist-tag add play-ts-package@1.1.0 branch/with-a-slash
   npm ERR! code E404
   npm ERR! 404 Registry returned 404 for PUT on https://registry.npmjs.org/-/package/play-ts-package/dist-tags/branch/with-a-slash

npm ERR! A complete log of this run can be found in: npm ERR! /Users/jessitron/.npm/_logs/2018-06-06T16_21_03_064Z-debug.log

3. publish the project again
4. observe a difference between `npm view` (shows the latest publish) and the website (does not show the post-failed-tag publish)

## Browser with version

Firefox 60.0.1

## Any error message?

only when adding the invalid tag. not on the website.

[jefflembeck]

Hey @jessitron, this issue seems to have cleared up. Is it fixed on your end as well?

[ShMcK]

Having the same issue with @rematch/core@1.0.4.

The slash is being interpreted as @rematch%2floading/dist-tags in the URL params