fix: use forward slashes in generated env.d.ts import path on Windows#15977
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: a176b19 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 |
`write_env` built the path with `path.relative`, which returns backslashes on
Windows. The path is interpolated into an `import('...')` type, where the
backslashes break module resolution and the env vars fall back to `any`. Wrap
it in `posixify`, matching how `write_tsconfig` already handles relative paths.
Fixes sveltejs#15959
Nic-Polumeyv
force-pushed
the
fix-env-dts-windows-path
branch
from
14da52c to
a176b19
Compare
Rich-Harris
pushed a commit
that referenced
this pull request
Jun 8, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @sveltejs/kit@2.63.1 ### Patch Changes - fix: use SSE for `query.live` ([#15957](#15957)) - fix: use forward slashes in the generated `env.d.ts` import path on Windows ([#15977](#15977)) - fix: allow `$app/environment` with a warning when `explicitEnvironmentVariables` is enabled ([#15980](#15980)) - fix: avoid importing Vite while validating explicit environment variables ([#15953](#15953)) - docs: adjust the release version of explicit env vars ([#15968](#15968)) - fix: ensure `version` is defined when importing from `$app/env` with explicit environment variables ([#15971](#15971)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #15959.
write_envbuilds the path withpath.relative, which returns backslashes on Windows. That value goes into animport('...')type in the generatedenv.d.ts, so the backslashes break module resolution and every explicit env var falls back toany. Wrapping it inposixifyfixes it, the same waywrite_tsconfigalready handles its relative paths.The broken import degrades the types to
anyrather than erroring, which is probably why it slipped through Windows CI even thoughoptions-2generates this file withexplicitEnvironmentVariablesenabled.Changesets