Skip to content

Remove the Next.js app - #3

Draft
TimMonko wants to merge 1 commit into
cf/01-data-repofrom
cf/02-remove-nextjs
Draft

TimMonko wants to merge 1 commit into
cf/01-data-repofrom
cf/02-remove-nextjs

Conversation

@TimMonko

Copy link
Copy Markdown
Member

npe2api served the API from Vercel with a Next.js app that read the
JSON under public/. plugin-api will serve the same paths from Cloudflare
as static files (the next PRs), so the app goes: pages/, package.json,
vercel.json, ESLint, and the Test workflow, which only linted and built
it.

Nothing live depends on this repository yet: api.napari.org is still
served by napari/npe2api on Vercel until the handover. At the handover,
npe2api becomes a redirect to api.napari.org, so npe2api.vercel.app (used
by napari up to 0.10.0 and plugin-manager up to 0.1.9) keeps working.


Stack created with GitHub Stacks CLI • Give Feedback 💬

@TimMonko
TimMonko added this pull request to stack #9 November 20, 2026 06:03
@TimMonko
TimMonko force-pushed the cf/02-remove-nextjs branch from a75fbfb to 8917bcb Compare November 20, 2026 06:25
npe2api served the API from Vercel with a Next.js app that read the
JSON under public/. plugin-api will serve the same paths from Cloudflare
as static files (the next PRs), so the app goes: pages/, package.json,
vercel.json, ESLint, and the Test workflow, which only linted and built
it.

Nothing live depends on this repository yet: api.napari.org is still
served by napari/npe2api on Vercel until the handover. At the handover,
npe2api becomes a redirect to api.napari.org, so npe2api.vercel.app (used
by napari up to 0.10.0 and plugin-manager up to 0.1.9) keeps working.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant