Proget upgraded 6 -> 2024. Scoped npm packages no longer accessible.

[infrastrcture_6303]

We were running Proget 6 and publishing scoped npm packages to it.
We just upgraded to 2024.8 (build 4).

Previously, our scoped packages appeared in the feed without the @ symbol.
Now, we're seeing a new package with the @ symbol. Trying to run npm install results in an error because it can't find the packages previously published under the non-@ symbol name.

How do I make 2024.8 compatible with the previous behaviour, or how do I rename all of the existing packages.

To be clear, on the client end, the package is scoped and has the @ symbol. It is only in Proget that the @ symbol seems to be have been getting removed previously.

[atripp]

Hi @infrastrcture_6303 ,

We've had one other user report this, and unfortunately it's a bit complicated behind the scenes. ProGet 6 allowed npm packages to be uploaded without a @ in the scope, which meant that if you used a non-npm client (your own script, etc), you could have "bad data" in the database.

We did not anticipate this data when doing the ProGet 2023 datamigration, so the bad data was brought over.

We don't have a means of fixing it, and it would take a nontrivial amount of time to do that - so as a free user we can't really put in that time. We do plan on a cleanup task ina few months that will take care of this automatically.

If you're comfortable with SQL, you may be able to fix it yourself (that's what the other user did), and it invovles a figuring out some queries around the PackageNameIds table.

Another alternative is to setup a new instance of ProGet 2024 and then just import the packages from disk.

Thanks,
Alana