NPM Package Registry Returns 404 with upstream package-lock.json #21567
Description
Description
The NPM package registry adds a /version in the URL that it uses to pull down the package tarball from the remote, and while this works when a repository has been configured to use Gitea alone, migrating projects back and forth from another registry (i.e. https://registry.npmjs.org/) requires you to delete (or otherwise update) the package-lock.json file for npm to resolve the package correctly.
Gitea Version
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
Screenshots
Git Version
2.38.0
Operating System
popOS 22.04
How are you running Gitea?
For this testing I was running it locally from a fresh copy built from main. Normally, however this server is ran inside of Kubernetes with the official Gitea chart (specifically https://dl.gitea.io/charts version: 6.0.1).
Database
SQLite