Bram del Canho

Recreated the PR because of a typo.

I created a new PR with a better version that has breaking changes.

Check out my PR: https://github.com/fastify/fastify/pull/5315 I am currently using my own fork to overcome this issue: https://github.com/Bram-dc/fastify/tree/separated-typeprovider With this type-provider: ``` /* eslint-disable @typescript-eslint/no-explicit-any */ import type { FastifyBaseLogger, FastifyInstance,...

Refs will be added once they find a matching object in the "components" objects. It uses JSON.stringify to check for this. It also checks for some common alterations like nullable....

No I have not, I can do tomorrow.

No, it does not unfortunately solve the issue. Maybe I should open a PR at shaka player to also create an esm build.

Make sure to disable the caching of the vite bundler when testing. It probably saved an earlier "optimized" version, as vite calls it, of the package. "optimized" meaning it created...

You can test it when the package is not cached using this: ``` optimizeDeps: { exclude: ['shaka-player/dist/shaka-player.ui'], }, ```

> It probably saved an earlier "optimized" version, as vite calls it, of the package. It also does this when running the bundler without any include. It probably does it,...

https://vitejs.dev/guide/dep-pre-bundling > During development, Vite's dev serves all code as native ESM. Therefore, Vite must convert dependencies that are shipped as CommonJS or UMD into ESM first. > When converting...