翠 / green

Are you directly reading those files from PHP (e.g. replacing text) and not simply referring in the rendered HTML? If you just need to refer it, you can just use...

Then, why do you need to copy the files? I think it's easier to just read the original files.

> Because we try to keep production files and the dev file separate. I see. Thanks for explaining. > If everybody would just put their files in the public folder,...

According to the docs, Vite supports transpiling module worker to classic worker. https://vitejs.dev/guide/features.html#:~:text=The%20worker%20script%20can%20also%20use%20import%20statements%20instead%20of%20importScripts()%20%2D%20note%20during%20dev%20this%20relies%20on%20browser%20native%20support%20and%20currently%20only%20works%20in%20Chrome%2C%20but%20for%20the%20production%20build%20it%20is%20compiled%20away. But it seems it is not working. It looks like a bug. https://stackblitz.com/edit/vitejs-vite-rkfhuq?file=main.js&terminal=dev

I don't think such a complicated approach is needed for this issue. IIUC @okikio is requesting for (correct me if I'm wrong): - reducing worker size (by tree-shaking) - wider...

https://github.com/vitejs/vite/issues/8466#issuecomment-1146655205 this seems to be fixed somewhere between 3.0.0-alpha.1 and 3.0.0-alpha.2.

@okikio > the current way vite supports iife is super buggy Would you expand this a bit more? BTW for now (3.0.0-alpha.10), generating both classic and module worker can be...

Maybe this issue can be closed by e58f6d6623ff8dc64b73e169a6deba5db89dd2fb?

Adding `` to each page might work. Algolia seems to support this. https://www.algolia.com/doc/guides/building-search-ui/resources/seo/js/#you-use-canonical-urls-to-indicate-primary-content

@HugoImaios I would appreciate it if you could open a pull request. 👍