* [Galene] Help with ES6 modules
@ 2024-11-16 21:55 Juliusz Chroboczek
0 siblings, 0 replies; only message in thread
From: Juliusz Chroboczek @ 2024-11-16 21:55 UTC (permalink / raw)
To: galene
Hi,
I've just started working on background blur in Galene's default client.
I'm using Google selfie segmentation library, which is available as an ES6
module. That's not a problem, since I'm planning to load it in a web
worker, so that the mail galene.js code does not need to become a module.
Still -- should I migrate the whole of the JS code in Galene to ES6
modules? In particular, would it inconvenience people if protocol.js
became an ES6 module? It is my (perhaps erroneous) understanding that
dynamic import is available in non-module code, so that the library will
continue to be usable, but is there anything I'm overlooking?
Thanks,
-- Juliusz
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-11-16 21:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-11-16 21:55 [Galene] Help with ES6 modules Juliusz Chroboczek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox