feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

feat: Vite environment API - #14008

Closed
teemingc wants to merge 20 commits into
mainfrom
environment-api
Closed

feat: Vite environment API#14008
teemingc wants to merge 20 commits into
mainfrom
environment-api

Conversation

@teemingc

@teemingcteemingc commented Jul 17, 2025

Copy link
Copy Markdown
Member

closes#13692
closes#1712
part of #3535
closes#13739
closes#13357
closes#12637

w.i.p and still has a lot of problems to solve. Needed to open this PR to test installing this from pkg.pr.new since linking locally with pnpm symlinks to the local kit repo. Then, when we try importing kit code from inside an environment, it results in a path which doesn't exist such as /packages/kit/.... Instead, it should probably import from node_modules/@sveltejs/kit/....

This PR adopts the Vite Environment API in kit and changes adapter-cloudflare to use a similar approach to Remix where the user can specify their own worker.js file. Otherwise, we can generate the wrangler config and worker for them. This approach integrates well with vite-plugin-cloudflare and provides users with direct access to the worker script, allowing them to export Durable Objects and add additional handlers.

Thanks to @jamesopstad for #12637 and writing up the Google Doc explaining the Remix and vite-plugin-cloudflare integration. Resources include:

TODO

  • Cloudflare dev
  • Cloudflare build
  • Node
  • vite-plugin-netlify
  • Vercel?
  • SPA/static?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot

changeset-botBot commented Jul 17, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7fdfe68

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 71e3d5a

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@teemingc
teemingc marked this pull request as draft July 17, 2025 05:26
@benmccann

Copy link
Copy Markdown
Member

You probably need to bump the peer dep version on Vite

@benmccannbenmccann added this to the 3.0 milestone Jul 17, 2025
@teemingc

teemingc commented Jul 18, 2025

Copy link
Copy Markdown
MemberAuthor

You probably need to bump the peer dep version on Vite

Thanks! I missed that. Bumped it to 7 because I think 6 is missing some Environment API behaviour around multiple plugins building the app

@svelte-docs-bot

Copy link
Copy Markdown

@umgefahren

This comment was marked as duplicate.

@didier

This comment was marked as duplicate.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Sorry this got paused for such a long time. Took a little time off from this since we were getting remote functions out, then I had some non-SvelteKit work too.

I left a bunch of TODOs in the code which should be enough to get started but I imagine resolving the merge conflicts since remote functions were merged would be step 1. The major goals are in the TODO list from the post at the top of the thread (get it working in cloudflare dev / vite dev). Hopefully I return to this this month if not next.

@Giggiux

Copy link
Copy Markdown

I am currently bypassing this issue using the approach defined in this repository, using alchemy.dev. But it adds a bunch of extra dependencies, it requires creating a new Worker script with the Durable Objects that after deployment is attached as a binding to the SvelteKit workers, and most importantly requires an "hack" in dev to send the requests via fetch to the secondary workers dev server, instead of using bindings.

Adding support for the official cloudflare vite plugin, and for websockets would make development with Cloudflare as a target even better with SvelteKit!

@Ayfri

This comment was marked as duplicate.

@Giggiux

Copy link
Copy Markdown

Hey @teemingc is there any way we can help in moving this PR forward?
I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

@teemingc

Copy link
Copy Markdown
MemberAuthor

Hey @teemingc is there any way we can help in moving this PR forward? I could try and spend some time on it, but I am very well conscious that I have no idea where to start.

Hey @Giggiux we’re waiting until SvelteKit 3 before we move to the environment API

@Giggiux

This comment was marked as off-topic.

hynj added a commit to hynj/kit-vite that referenced this pull request Dec 17, 2025
- Upgrade to Vite 7.0.3 and add pnpm override to ensure consistent versions
- Add sveltekit_vite_environment virtual module for dev-time manifest access
- Add DevEnvironment type for sharing state between plugin and dev server
- Add environment.js utilities for module resolution in Vite environments
- Update dev server to populate and invalidate environment module
- Support environments config for future isolated builds
This is a minimal port of the Environment API changes from PR sveltejs#14008,
enabling Vite 7 support while maintaining compatibility with existing
adapters.
@teemingc

Copy link
Copy Markdown
MemberAuthor

Closing this because we'll be starting this from scratch next week

@teemingcteemingc closed this Feb 5, 2026
@kvanbere

Copy link
Copy Markdown

Is there a new PR for it?

Comment threadpackage.json
]
],
"overrides": {
"esm-env": "github:benmccann/esm-env#bcbddbc&path:packages/esm-env"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, is there a reason you had to do this? is there anything you need me to fix in it?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petebacondarwin

Copy link
Copy Markdown

Is there a new PR for it?

This I think: #15627

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom worker script when deploying to Cloudflare Cloudflare Worker Adapter - Durable Objects

8 participants

@teemingc@benmccann@umgefahren@didier@Giggiux@Ayfri@kvanbere@petebacondarwin