2 ms·
Ah, I see what you mean. You were talking about using imports recursively. I use fetch instead of imports for web components because I have a web component tha
by lelanthran 2mo ago
Ah, I see what you mean. You were talking about using imports recursively.
I use fetch instead of imports for web components because I have a web component that does client-side includes, and it's literally easier to do client-side includes in a performance manner than anything else, including the recursive case.
- troupo 2mo agoSo we're back to my original comment: https://news.ycombinator.com/item?id=49131513 https://news.ycombinator.com/item?id=49131513 Yes you can invent all kinds of workarounds for their core design. Re-implementing imports like you do. Or bundling, like everyone does and something that even lit recommends: https://lit.dev/docs/tools/production/ https://lit.dev/docs/tools/production/
- lelanthran 2mo ago> So we're back to my original comment: https://news.ycombinator.com/item?id=49131513 https://news.ycombinator.com/item?id=49131513 And we're back to my original comment - imports get served from the local cache, so a bit of a nothing-burger in the great scheme of things.
- troupo 2mo agoExcept cache is not infinite, it is routinely expunged and re-fetched. The "nothing burger" is so significant that even projects whose stance is "web components are the end all be all of web development" like lit recommend bundling.