nextjs-monorepo-example
react-i18next
nextjs-monorepo-example | react-i18next | |
---|---|---|
19 | 71 | |
1,465 | 8,942 | |
- | 0.8% | |
9.9 | 8.8 | |
7 days ago | 11 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nextjs-monorepo-example
-
TypeScript monorepo
For info you can have a look to a setup in httpx (simple yarn 4 + workspaces) or nextjs-monorepo-example (yarn 4 workspaces + turbo + recipe for docker)
-
Why Next?
I like https://github.com/belgattitude/nextjs-monorepo-example/
-
How do you keep FE dependencies up to date?
It's pretty easy to setup renovate, the "update dependency XXX PR" comes with the upstream changelogs from which you can have an idea of the work to do if needed. Compared to some other similar tools: monorepo support (ie: workspace:"") + possibility to dedupe your lock file + an easy way to regroug packages (ie: "@vitest/ui" and "vitest" together). An example: https://github.com/belgattitude/nextjs-monorepo-example/blob/main/renovate.json5.
-
Separating components from Next.js in a mono repo
https://github.com/belgattitude/nextjs-monorepo-example Here is a very good example monorepo with a similiar usecase
-
Eslint warnings in neovim but not vscode
Until the “flat” eslint config file becomes the standard, Here’s a nice example of how to do it.
-
is nx worth it for a smallish typescript monorep?
PS: You can see there: https://github.com/belgattitude/nextjs-monorepo-example (bunch of recipes but definitely needs a cleanup) and this question https://github.com/belgattitude/nextjs-monorepo-example/discussions/2220
-
Best way to deal with long background jobs when deploying Next.js to Vercel?
There is one moderately complex example monorepo that includes a Next.js project and shared lib projects here: https://github.com/belgattitude/nextjs-monorepo-example
-
Looking for the right project structure for multiple teams (monorepo vs separate repos)
I sometimes put some examples in https://github.com/belgattitude/nextjs-monorepo-example. It's bare-bone and offer few pros/cons (no nx, no turbo.., but you can upgrade along the way).
-
which solutions do you use for i18n in typescript?
But if you have time, you can have a look to this https://github.com/belgattitude/nextjs-monorepo-example/blob/main/apps/web-app/src/features/demo/demo.config.ts.
-
Next.js monorepo build process optimization
- If you're using yarn 1, go yarn 3+ with "node_linker: node_modules", eventually "nmMode: hardlinks-local" and yarn workspace plugin (example of .yarnrc.yml config). You'll get some speed up and the update should not be too long to do. Note: this gives comparable speed of pnpm in my experience (whatever benchmark I read).
react-i18next
-
A brief history of web development. And why your framework doesn't matter
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.
Would you like to elaborate on that?
In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.
For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/
Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/
Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main
Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/
React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.
Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
-
Pains and solutions in localization for the web
In a recent project I've been using react-i18next so I'll use its syntax for the examples, but pretty much every library works similarly.
-
45 NPM Packages to Solve 16 React Problems
react-i18next
-
React Ecosystem in 2024
i18next - You can find documentation and resources for using i18next at react.i18next.com. i18next is a popular internationalization framework for JavaScript, including React. It provides a comprehensive solution for handling translations, formatting, and more.
-
Enforcing Localization through Types
So far, we’ve been using a utility createLocalizedString to create and use the LocalizedString type. This utility is only really practical in unit tests. For real applications, we’ll want to use a translation function from react-i18next or next-i18next to do the heavy lifting. Then we just wrap the translation functions that are provided in order to use our type:
-
5 Not-So-Typical React Libraries for an Outstanding Project
Website: https://react.i18next.com/
-
Is it a good practice to centralized messages file
If you are talking about handling translations for your application, take a look at https://react.i18next.com/
-
Looking for a few iOS devs that are interested in getting their apps localized.
I will be supporting Korean as a part of the beta. I have to look deeper into https://react.i18next.com/ in order to understand what it provides. My goal is for engineers to be able to click a single button and have localizations always up to date in their codebase, not delaying shipping a new version or having to even think about it.
-
Supercharge Your TypeScript App: Mastering i18next for Type-Safe Translations
With the new react-i18next version, when loading multiple namespaces, t function will infer and accept the keys for the first namespace. So this pattern is now accepted:
-
React Ecosystem in 2023.
react-i18next
What are some alternatives?
next-i18next - The easiest way to translate your NextJs apps.
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
nextron - ⚡ Next.js + Electron ⚡
i18next - i18next: learn once - translate everywhere
transloco - 🚀 😍 The internationalization (i18n) library for Angular
electron-react-boilerplate - A Foundation for Scalable Cross-Platform Apps
react-globalize - Bringing the i18n functionality of Globalize, backed by CLDR, to React