`$page.url.pathname` represented as "//prerender/" when building using the static adapter

Describe the bug

Using the latest versions:

• @sveltejs/kit version 1.0.0-next.211
• @sveltejs/adapter-static version 1.0.0-next.24

In development, $page.url.pathname in routes/index.svelte will correctly be displayed as “/”.

However, when building for production using the static adapter, the same route is represented as “//prerender/”.

Inspecting build/index.html, the markup has the correct “/” but the script that hydrates the markup has the following:

<script type="module">
  import { start } from "/_app/start-40ff21d5.js";
  start({
    target: document.querySelector("#svelte"),
    paths: { base: "", assets: "" },
    session: {},
    route: true,
    spa: false,
    trailing_slash: "never",
    hydrate: {
      status: 200,
      error: null,
      nodes: [
        import("/_app/layout.svelte-96b29dd0.js"),
        import("/_app/pages/index.svelte-91ca303b.js"),
      ],
      url: new URL("sveltekit://prerender/"),
      params: {},
    },
  });
</script>

Evaluating new URL("sveltekit://prerender/") shows that the URL.pathname is //prerender/.

Workaround

A workaround is to explicitly set kit.ssr or kit.hydrate to false.

Reproduction

https://github.com/metonym/sveltekit-page.url.pathname

Logs

No response

System Info

System:
  OS: macOS 11.4
  CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
  Memory: 19.40 MB / 16.00 GB
  Shell: 5.8 - /bin/zsh
Binaries:
  Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
  Yarn: 1.22.17 - /usr/local/bin/yarn
  npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Browsers:
  Chrome: 96.0.4664.110
  Firefox: 89.0.2
  Safari: 14.1.1
npmPackages:
  @sveltejs/adapter-static: next => 1.0.0-next.24 
  @sveltejs/kit: next => 1.0.0-next.211 
  svelte: ^3.44.0 => 3.44.3

Severity

blocking an upgrade

Additional Information

No response

[brittneypostma]

Same here, after updating to latest, this issue seems to have been resolved.

[metonym]

I updated the repro to use the latest SvelteKit (v1.0.0-next.231) and also added console.log($page.url.pathname) to routes/index.svelte. I’m no longer seeing this error.

After building using the static adapter, I see “/” in the console, as expected.