Cutover needs a redirect path for /packages/* and /bundles off mpak.dev

Open
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cloud, github

Research direction

Read issue #164's deploy-coupling section and the comment in apps/web/src/routes/bundles.tsx, then inspect the Pages and DNS cutover setup to identify where redirects can be handled. Name a mechanism that routes all 41 /packages/* URLs and /bundles from mpak.dev to their new home, add it to #164's deploy-coupling list, and confirm it before DNS moves.

Written by the indexing model from the issue text.

Description

pkg/web

Package pages are live on mpak.dev today:

$ curl -s -o /dev/null -w "%{http_code}\n" https://mpak.dev/packages/@nimblebraininc/echo
200

After the cutover in #164, mpak.dev is GitHub Pages and registry.mpak.dev serves the app. All 41 package URLs plus /bundles need to reach their new home, or they answer with the Pages 404.

Two things make this harder than the /sitemap.xml and /feed.xml items already listed in #164's deploy-coupling section:

  • GitHub Pages cannot issue a 301. Serving a page at the old path or a meta-refresh shim passes far less link equity than a real redirect, so the mechanism likely has to sit in front of Pages (CloudFront) rather than in mpak-web.
  • /bundles is linked from the marketing site, the docs, and CLI output, per the comment in apps/web/src/routes/bundles.tsx. The app redirects /bundles to / on the new host, but nothing catches the old host's /bundles.

mpak-web PR #5 stands up the Pages deploy and touches no routing, so this is unowned right now.

Add /packages/* and /bundles to #164's deploy-coupling list with a named mechanism, and confirm it before DNS moves.

Dominant language
TypeScript
Stars
14
Forks
13
Avg merge
16m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NimbleBrainInc/mpak

All issues in NimbleBrainInc/mpak

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.