fix: omit ISR data endpoints for server-only routes - #16731
Conversation
|
Install the latest version of pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/0e50024c99994ce7855fb1b79c5b66530fe3bad9Open in Note This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed. |
🦋 Changeset detectedLatest commit: 0e50024 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
4cbac70 to
0e50024
Compare
|
Rebased this PR onto the latest I attempted both the adapters complete test command and its focused unit/build halves locally. In this workspace each hung without output until the command timeout/interrupt, so I did not claim a local pass for the rebased head. The previous heads GitHub CI was green; the newly pushed head is |
closes #12690
Server-only ISR routes do not have a page data endpoint, but the Vercel adapter currently emits a data function, prerender configuration, and routing entry for them.
This change only creates those data-specific ISR artifacts when a route has page methods. The server route main function, prerender configuration, and routing entry remain unchanged.
The build regression adds ISR to the existing API fixture and verifies that its main artifacts are present while its data artifacts are absent. It also verifies that a regular ISR page still keeps its data function and route.
Please do not delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
Changesets
Edits