Tom Lienard

I'll research a bit more about catching errors from effects before merging, because `componentDidCatch` currently only works for (re)render errors.

Found an issue with the changes inside the Vite plugin, it was throwing an error and such fail to transform the AST. Fixed by only adding the `_parent` to the...

I did a very basic PoC that adds `componentDidCatch` to class components from errors caught on `render`. I'm not sure if adding a `useErrorBoundary` hook makes sense for Million? (And...

Reopening this issue since #258 doesn't completely fix the bugs - but fixes some of them.

There are a few reasons why this library currently only works with Next.js: - `getStaticProps` allows to serve content in multiple languages while having good Web Vitals and SEO, although...

Agree that `I18nProvider` & `useI18n` can be easily extracted into a standalone package. But one of the goals of this library is to have everything ready-to-go, with minimal/no extra configuration....

Thanks for the kind words! Yeah, splitting the types into a separate package is something that I want to do, so anyone can use them with the library they want....

Started working on a type-specific package: - https://github.com/QuiiBz/next-international/pull/20 Update: `international-types` released on NPM and used by `next-international` starting `0.1.1`

Thanks for the kind words! Cool idea, but I think you are losing parameters type-safety due to the generic of `createI18n`: `Record` ..................................................^ due to this `string`, you won't be...

A more descriptive box seems like a good idea, but I feel like it's a bit strange to hide the whole autocomplete suggestions. I came up with this idea (badly...