vcarl
RReactiflux
•Created by Sniberb on 8/23/2024 in #help-js
snowberb – 20-34 Aug 23
The frontend developer roadmap has a good list of concepts, which is decent for discovering concepts to study at least https://roadmap.sh/frontend
9 replies
RReactiflux
•Created by drilkmops on 8/19/2024 in #help-js
drilkmops – 15-59 Aug 19
yea 400kb for a i18n runtime is :sus:
42 replies
RReactiflux
•Created by drilkmops on 8/19/2024 in #help-js
drilkmops – 15-59 Aug 19
Ah yeah I think I had assumed you were already splitting on locale
42 replies
RReactiflux
•Created by drilkmops on 8/19/2024 in #help-js
drilkmops – 15-59 Aug 19
I guess, the hardest part here to me seems like it's understanding which source strings are in what code and ensuring that a minimal set of strings gets loaded
42 replies
RReactiflux
•Created by drilkmops on 8/19/2024 in #help-js
drilkmops – 15-59 Aug 19
I guess I'm suggesting re-implementing some of the chunking and script/resource loading logic that would otherwise be done by something like webpack, as a means of avoiding tool lock-in. I'm not sure what that would look like in practice tho, it might be too big.
42 replies
RReactiflux
•Created by drilkmops on 8/19/2024 in #help-js
drilkmops – 15-59 Aug 19
afaik this is how most i18n libraries I've used have worked, they tap into the compilation/build step and work to make resources available that way. But, that's meant that they have e.g. babel transforms and webpack plugins, which locks them into specific build tools
I wonder what it would look like to think about this from the web platform, rather than the build tool ecosystem? e.g. webpack is managing a tree of dependencies to ensure
<script>
tags get added to the dom and are ready to execute as user code expects — I wonder if it'd be feasible to do something similar for i18n?42 replies