How to make SvelteKit HMR work with Gitpod

Thilo Maier •
Last modified:

This post is outdated. HMR works just fine on Gitpod with SvelteKit 1.x.

SvelteKit uses Vite with vite-plugin-svelte to implement hot module replacement (HMR). HMR ensures that changes in your code are reflected instantly in your browser preview. This results in a pleasant developer experience. HMR in SvelteKit works out of the box with no configuration required.

Why HMR on Gitpod is different

Things change when you develop with a cloud workspace such as Gitpod. If you are not familiar with cloud workspaces, check out my post A better development workflow with disposable workspaces. In a Gitpod workspace, the SvelteKit development server runs on port 5173, like in your local development environment. How you access the development server depends on how you access your Gitpod workspace:

  • When you access a Gitpod workspace from within a browser, you can access the development server with an external URL on the domain. To make this work, Gitpod proxies to the external URL.
  • When you access your Gitpod workspace from VS Code via SSH, VS Code proxies the development server to You work with your Gitpod workspace as if it was a local development environment.

While developing a SvelteKit app with Gitpod inside a browser, I noticed that HMR was broken. It would trigger indefinite page reloads after firing up the SvelteKit development server. Like in this GitHub issue. The last issue comment points to the solution. You can customize the Vite configuration and override its default HMR behavior.

The Vite docs explain that

clientPort is an advanced option that overrides the port only on the client side, allowing you to serve the websocket on a different port than the client code looks for it on. Useful if you're using an SSL proxy in front of your dev server.

Vite brokers between the external URL and the development server running in your Gitpod workspace.

Gitpod workspace URLs

A Gitpod workspace is available at a unique URL (which requires authentication) with the following format:


Every Gitpod workspace sets GITPOD_WORKSPACE_URL, which contains the unique workspace URL.

By default, a development server is not accessible externally. You need to tell the workspace which internal port it should expose. If e.g., your development server runs at you need to add the following configuration to your .gitpod.yml:

    # Expose port 5173.
  - port: 5173

    # Install dependencies.
  - init: npm install
    # Run SvelteKit dev server (which uses port 5173).
    command: npm run dev

tasks defines tasks that Gitpod runs when it initializes the workspace. This configuration makes the development server available at this URL:


E.g., I wrote this post on a Gitpod workspace running at

The workspace ID maiertech-maiertech-ti2zaqimh33 consists of my GitHub username maiertech, an ID derived from the repository name and a UUID. With the above .gitpod.yml configuration, the SvelteKit development server of this workspace can be reached at

You can access the development server only when authenticated to Gitpod.

Overriding HMR in vite.config.js

Next, we override a the HMR configuration in vite.config.js:

// ...
server: {
  hmr: {
    clientPort: process.env.GITPOD_WORKSPACE_URL ? 443 : 5173,
    host: process.env.GITPOD_WORKSPACE_URL
      ? process.env.GITPOD_WORKSPACE_URL.replace('https://', '5173-')
      : '',

// ...

We set clientPort and host depending on whether GITPOD_WORKSPACE_URL exists. This ensures that HMR works when running your Gitpod workspace inside a browser. But also for anyone running the SvelteKit site in a local development environment.

There is a catch with this Vite configuration. GITPOD_WORKSPACE_URL also exists in a Gitpod workspace, which runs in a local VS Code via SSH. In this scenario, you can access the development server on But the above Vite configuration expects it to be on a URL.

Thus, you should add the custom Vite configuration only if you plan to access Gitpod workspaces from within a browser. If you access Gitpod workspaces from within a local VS Code, you do not need the custom HMR configuration.

Browser extensions that interfere with HMR

One final word of caution. Even with the custom Vite configuration in place, HMR would still break for me. I narrowed this issue down to my browser extension uBlock Origin being the culprit. Any other ad blocker extension might interfere, too. So, I added to trusted sites in uBlock Origin.


Thanks to Mike Nikles from Gitpod for pointing me in the right direction when I ran into HMR issues with SvelteKit on Gitpod. Gitpod's website is written in SvelteKit and open source. You can learn a lot from this repository.