KevinCarnaille

Did you guys found a solution ? The issue is the same with `www/build` repository, all files are not hashed (espacially the files we need to use :) )

Since 2019 there are no decent way to fix it ? I'm not sure to understand what you mean by "reexport the instance" though ?

FYI, still having the issue in Stencil `2.17.3` :) @thccorni workaround is working ;)

Hello there, I had the issue for a while and indeed, I'm using multiple output targets (stencil 2.18.0) Fixed the issue by removing the `dist-hydrate-script` output (https://stenciljs.com/docs/hydrate-app#how-to-use-the-hydrate-app) I don't use...

Don't know if it can help, my 2 cents : I got the warning as soon as I include the `dist-custom-element ` in `outputTarget`. I have no warning if I...

Any update about the prioritization ? Facing the same issue and use pre-hydration style for most of my library. I can only use `dist` atm :)

Hi @rwaskiewicz I still have the warning in 3.3.0, but I've tried the `4.0.1-dev.1688059870.bea1aeb` and it's fixed !

Despite `dist-hydrate-script` itself, it's actually a useful feature to set hydrated with **attribute** instead of **class**, because it's very common to use custom classes on our tags when implementing them....