You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare v0.svelte.stackoverflow.design to serve legacy Svelte documentation through the existing Netlify project. Keep the shared v2 Git branch and its branch deployment as the content source.
This is the routing preparation only; the new domain alias and live verification follow after deployment.
Changes
Upgrade HTTP requests for the v0 hostname to HTTPS.
Proxy HTTPS v0 requests to v2--stacks-svelte.netlify.app with a forced 200 rewrite.
Preserve the existing beta redirect and leave current documentation, previews, and the old v2 hostname unchanged.
Check each routing block independently in regression tests.
No dependency changes, package version bump, or changeset: this affects hosting configuration only.
How to test
Run npm ci, then node --test packages/stacks-svelte/tools/netlify-config.test.js. All four focused checks passed.
Run npm run lint -w packages/stacks-svelte, npm run build -w packages/stacks-svelte, and npm run test -w packages/stacks-svelte. Passed: zero Svelte diagnostics, 591 browser tests, and 32 Node tests. Existing Storybook deprecation and chunk-size warnings remain.
Check the Svelte deploy preview if generated. Current documentation should remain accessible without redirecting.
After production deployment, add v0.svelte.stackoverflow.design as a production domain alias. Verify HTTPS, legacy content, Storybook navigation, component assets, and query preservation while the browser URL stays on v0.
Keep the v2 branch deployment enabled. Do not move the old hostname or update public links until the live proxy checks pass. Same-project branch proxying remains unverified until this step.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare
v0.svelte.stackoverflow.designto serve legacy Svelte documentation through the existing Netlify project. Keep the sharedv2Git branch and its branch deployment as the content source.This is the routing preparation only; the new domain alias and live verification follow after deployment.
Changes
v0hostname to HTTPS.v0requests tov2--stacks-svelte.netlify.appwith a forced 200 rewrite.v2hostname unchanged.How to test
npm ci, thennode --test packages/stacks-svelte/tools/netlify-config.test.js. All four focused checks passed.npm run lint -w packages/stacks-svelte,npm run build -w packages/stacks-svelte, andnpm run test -w packages/stacks-svelte. Passed: zero Svelte diagnostics, 591 browser tests, and 32 Node tests. Existing Storybook deprecation and chunk-size warnings remain.v0.svelte.stackoverflow.designas a production domain alias. Verify HTTPS, legacy content, Storybook navigation, component assets, and query preservation while the browser URL stays onv0.v2branch deployment enabled. Do not move the old hostname or update public links until the live proxy checks pass. Same-project branch proxying remains unverified until this step.