Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions packages/kit/src/exports/vite/index.js
Original file line number Diff line number Diff line change
Expand Up @@ -1975,12 +1975,6 @@ function kit({ svelte_config }) {
if (service_worker_entry_file) {
log.info('Building service worker');

// mirror client settings that we couldn't set per environment in the config hook
builder.environments.serviceWorker.config.define = {
...builder.environments.client.config.define,
...builder.environments.serviceWorker.config.define
};

builder.environments.serviceWorker.config.resolve.alias = [
...get_config_aliases(kit, vite_config.root)
];
Comment on lines 1978 to 1980

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.

Suggested change
builder.environments.serviceWorker.config.resolve.alias = [
...get_config_aliases(kit, vite_config.root)
];

We ought to get rid of this too. It was only there to avoid resolving the __SERVER__ alias but we now use this setting for much more than that. Ideally, we'd still remove __SERVER__ somehow but maybe it doesn't matter?

@teemingc teemingc Aug 18, 2026 •

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.

Here's what the service worker allows resolving to if not overridden:

[
  {
    find: '__SERVER__',
  },
  {
    find: '$app',
  },
  {
    find: '$env',
  },
  {
    find: '<sveltekit:generated>',
  },
  {
    find: '__sveltekit/server',
  },
  {
    find: /^\/?@vite\/env/,
  },
  {
    find: /^\/?@vite\/client/,
  }
]

Expand Down
Loading