Svelte 5: New ownership check - original is undefined, therefore can't read original.filename

[ndom91]

Describe the bug

Upgraded from next.54 -> next.63 and began seeing hydration errors on every page load. See log below.

Error is pointing at this chunk of code in the new ownership.js file add in this PR

Reproduction

Sorry I know its not a minimal reproduction, but one of these:

cp .env.example .env && pnpm install && pnpm dev

should get you started in my project's repo here (linking to a specific commit).

The error does appear on the signin page before anything else has really been loaded or anything.

Logs

(index):929 ERR_SVELTE_HYDRATION_MISMATCH: Hydration failed because the initial UI does not match what was rendered on the server. TypeError: Cannot read properties of undefined (reading 'filename')
    at check_ownership (chunk-BXEGLMDE.js?v=53b432e9:1919:16)
    at Object.set (chunk-BXEGLMDE.js?v=53b432e9:1795:7)
    at root.svelte:47:69
    at chunk-7P3WBFNS.js?v=53b432e9:2947:21
    at untrack (chunk-BXEGLMDE.js?v=53b432e9:1120:12)
    at chunk-7P3WBFNS.js?v=53b432e9:2947:7
    at execute_signal_fn (chunk-BXEGLMDE.js?v=53b432e9:429:7)
    at execute_effect (chunk-BXEGLMDE.js?v=53b432e9:558:31)
    at schedule_effect (chunk-BXEGLMDE.js?v=53b432e9:633:7)
    at internal_create_effect (chunk-BXEGLMDE.js?v=53b432e9:1136:5)

System Info

System:
    OS: Linux 6.7 EndeavourOS
    CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
    Memory: 10.06 GB / 31.27 GB
    Container: Yes
    Shell: 5.2.26 - /bin/bash
  Binaries:
    Node: 20.9.0 - /run/user/1000/fnm_multishells/1575959_1708441177622/bin/node
    Yarn: 1.22.21 - /run/user/1000/fnm_multishells/1575959_1708441177622/bin/yarn
    npm: 10.1.0 - /run/user/1000/fnm_multishells/1575959_1708441177622/bin/npm
    pnpm: 8.14.3 - /run/user/1000/fnm_multishells/1575959_1708441177622/bin/pnpm
    bun: 1.0.1 - ~/.bun/bin/bun
  Browsers:
    Chromium: 121.0.6167.160
  npmPackages:
    svelte: 5.0.0-next.63 => 5.0.0-next.63 

Severity

blocking an upgrade

[Conduitry]

There was a fix for an instance of ERR_SVELTE_HYDRATION_MISMATCH in the just-released next.64. Does that resolve things for you?

[ndom91]

Ahh that was it. I just uninstall, reinstalled svelte@next and all of a sudden it worked. I couldn't believe my eyes.

Upon double checking you're right though, looks like a next.64 snuck out in between my uninstall/re-install.

Anyway, long story short - looks like its working again, thanks!