Miguel Ángel Durán

Sí, al final lo que se podría hacer es un dark mode a mano, que era la idea original. Habría que sacar tiempo y usar más las variables para hacerlo....

Interesting. Tricky but not impossible. You could try to move the provider inside the ProgressiveHydration component instead. This should enable the context to be available inside the progressive hydrated content...

But, is the solution working? There's no problem duplicating the i18n context provider. In fact, using Context.Provider more than once could be typical for some cases. As it's using internally...

Yes, sadly, I would say is a limitation for the strategy as well. :( As you said, duplicating these contexts will create two states for it and thus won't share...

LGTM!

@developit what help do you need to get this merged? I may help and I'm pretty interested on having this merged. :)

@alireza-mh the problem is that what you're bundling is, probably, already compiled. For example, `react` and `react-dom` are already transpiled. Almost everything that's already in your `node_modules` is, in fact,...

I think it's related to this: https://github.com/npm/cli/issues/3257

You could try to execute this using `DEBUG=* npm install` so more output could be provided. :)

¡Gracias por la PR! Creo que sería mejor separar lo que es inicializar algo con React a pelo (CRA y Vite) y, a parte, hacerlo con un framework como Next.js...