Hls.js does not work with SvelteKit (vite)

[codercms]

What version of Hls.js are you using?

1.2.9

What browser (including version) are you using?

Firefox 108.0.2

What OS (including version) are you using?

Win 10

Test stream

No response

Configuration

{}

Additional player setup steps

No response

Checklist

• The issue observed is not already reported by searching on Github under https://github.com/video-dev/hls.js/issues
• The issue occurs in the stable client (latest release) on https://hls-js.netlify.com/demo and not just on my page
• The issue occurs in the latest client (main branch) on https://hls-js-dev.netlify.com/demo and not just on my page
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream

Steps to reproduce

1. Install fresh version of SvelteKit
2. Install hls.js (npm i hls.js --save-dev)
3. Import hls.js into your component (import Hls from 'hls.js')
4. Try to load and play video

Expected behaviour

hls.js should work

What actually happened?

hls.js failed with TypeError: __webpack_modules__2[moduleId] is undefined error

See reproduction in stackblitz - https://stackblitz.com/edit/vitejs-vite-jhuctn?file=src%2FApp.svelte

P.S. Related issue - #5146
hls.js works fine if import it like this: import Hls from "hls.js/dist/hls.min.js";

Console output

TypeError: __webpack_modules__2[moduleId] is undefined

Chrome media internals output

No response

[laurens94]

It seems the combination of Vite v4 with hls.js causes this. Downgrading vite from 4.0.0 to 3.2.5 and @vitejs/plugin-vue from 4.0.0 to 3.2.0 'solved' this issue for me.

Perhaps it's related to the upgrade to Rollup v3 in the latest Vite version?

For me the issue only occured when running the code locally with vite dev server. Building with vite build and then running the output code didn't give any error.

[laurens94]

Ah I just stumbled upon this issue #5107 which should fix it.

[jer-0]

@robwalch doesn't 1.4.0 fixes this?