Vite 4.1+ causes block.l is not a function error on HMR during dev

[smblee]

Describe the bug

Upgrading to vite 4.1+ from 4.0.4 causes HMR to not work with pages with ValidationMessage component with the error [HMR][Svelte] Unrecoverable HMR error in <Root>: next update will trigger a full reload and block.l is not a function and crashes.

Seems to be due to but i am not too sure:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'classList')

Currently i have to resolve to not upgrading vite to 4.1+

Which package/s are you using?

felte (Svelte)

Environment

• OS: M1 Macbook Pro
• Browser: Chrome
• Version: felte@1.2.7, @felte/reporter-svelte@1.1.5, @felte/validator-zod@1.0.13

To reproduce

No response

Small reproduction example

No response

Screenshots

No response

Additional context

No response

[endigma]

Can confirm, completely breaking

[fehnomenal]

We need the source of ValidationMessage.svelte exported.

Source: nolimits4web/swiper#4013

Adding "./ValidationMessage.svelte": "./src/ValidationMessage.svelte" to the package.json works.

[teenjuna]

+1

[JLAcostaEC]

+1

[knakamura13]

Still broken.

I tried adding "./ValidationMessage.svelte": "./src/ValidationMessage.svelte" to the "exports" section of the file ./node_modules/@felte/reporter-svelte/package.json, but the error persists.

[TimoWilhelm]

My current workaround is wrapping the <ValidationMessage> in <OnMount> blocks. It's definitely not optimal and I'd like to remove it in the future, but it allows me to continue working with HMR for now.

<OnMount>
  <ValidationMessage for="fruits" let:messages>
    ...
  </ValidationMessage>
</OnMount>

OnMount.svelte

<!-- Mounts a component when the DOM is ready. Useful for intro animations -->
<script>
  import { onMount } from 'svelte';

  let mounted = false;
  onMount(() => {
    mounted = true;
  });
</script>

{#if mounted}
  <slot />
{/if}

[gl-aagostino]

@TimoWilhelm Thank you for this!

[baseplate-admin]

Probably fixed by #237

Please check :)

[baseplate-admin]

@pablo-abc I think we can close this issue.

I been testing felte on a production site for months without any error on svelte 4