René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Legacy Package Capitalization Mismatch after CF Worker Migration","articleBody":"First off, thanks for putting together such an awesome tool! \n\nI noticed that in the past few weeks, around the time of the cutover to the new Cloudflare Workers stack, that references to `gaugeJS` via unpkg.js have stopped working with a response of `Package not found: gaugeJS` whereas they previously returned the referenced file contents for the specified package name + version. \n\n\n## gaugeJS example\n**URL**:\n https://unpkg.com/gaugeJS@1.3.8/dist/gauge.min.js\n\n**Actual Response**:\n```\nPackage not found: gaugeJS\n```\n**Expected Response**:\n  \nContents of the gaugeJS `/dist/gauge.min.js` file for the `1.3.8` version on npm. This is what was returned just a few weeks ago - likely prior to the CF Worker cutover. \n\n## Legacy Uppercase\nI suspect this is related to the use of capitalization with the package name which was [allowed in npm legacy packages](https://github.com/npm/validate-npm-package-name/tree/main?tab=readme-ov-file#legacy-names), but is somewhat uncommon as most packages follow the new all lowercase requirements. \n\n## Alternate Example\nIt was a bit difficult to find another example, but you can see that `Angular2` is quite different from `angular2` but it seems like the new CF Worker approach normalizes to the lowercase variant. You would expect [unpkg.com/Angular2/](https://unpkg.com/Angular2/) to point to the [Angular2 npm package](https://www.npmjs.com/package/Angular2) for TypeScript snippets, but instead unpkg provides a 301 to `/angular2@2.0.0-beta.21` matching the lowercase [angular2 npm package](https://www.npmjs.com/package/angular2). \n\n\u003c!-- \n## Comment References - CF Worker Cutover\nFor other people finding this issue, here's the comments I was referring to about the recent CF Workers cutover:\n\n\u003e My apologies for the issues you all experienced this week. We are experiencing some growing pains, but we finished a migration to a completely new stack this week that should help us scale into the future. ([#440 Comment](https://github.com/unpkg/unpkg/issues/440#issuecomment-2781010043))\n\n\u003e We've been migrating all our traffic away from our origin servers towards a new service built on CF workers. ([#449 Comment](https://github.com/unpkg/unpkg/issues/449#issuecomment-2781007003))\n--\u003e","author":{"url":"https://github.com/joshualyon","@type":"Person","name":"joshualyon"},"datePublished":"2025-04-11T19:44:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/453/unpkg/issues/453"}