jsLingui
monorepo
Our great sponsors
jsLingui | monorepo | |
---|---|---|
9 | 56 | |
4,204 | 962 | |
1.7% | 7.1% | |
8.8 | 10.0 | |
4 days ago | 1 day ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
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.
jsLingui
-
What is the best way to handle a multi-language site?
https://lingui.dev/ by far.
-
Advanced enterprise localisation process with Lingui, Locize, Github Actions, Docker, React
We choose lingui.
- We will OSS the NextJs + web3 starter kit
-
Next.js internationalization (i18n) tutorial
As we mentioned earlier, the Next.js works well with existing i18n libraries (react-intl, lingui, next-intl, and similar). In this tutorial, we will use the react-intl.
-
I want multiple language support for my React project, what's the best way of doing it?
We use LinguiJS on a medium sized project and find it to work really well. Itβs small, supports multiple message formats, has CLI scripts for extracting message ids from source, JS apis, Babel macros, React components and hooks, webpack and snowpack plugins, good pluralization support and much more.
-
Handling i18n the proper way
I really like https://lingui.js.org/. It will create the .json or .po for you. And the component is just π.
-
which solutions do you use for i18n in typescript?
I'm a fan of Lingui. I use it for instant.bible.
-
Best Libraries for React I18n in 2021
Lingui JS
-
i18n and Next.js
lingui
monorepo
- Writing a document with version control feauters
-
Ask HN: What happened to startups, why is everything so polished?
fixed the capitalization https://github.com/opral/monorepo/commit/6127c6899290b35442c...
-
I build a free tool for software localization due to my pain, and now I need the community feedback. Please, try and let me know what you think ποΈ
Hey there! Have you ever heard about inlang (inlang.com)? Your approach goes in our direction. Great to see so many people fixing the i18n pain! :)
-
Supercharging Your App Development: Unleashing the Full Potential of React Native
If you want to take a look, here is the website featuring our products: https://inlang.com/
-
I got a job by posting here
Last time I posted on this Subreddit I was announcing my typesafe i18n library. As luck would have it some people at Inlang saw that post and my project and contacted me to work on ParaglideJS.
-
Best approach for CSR and SSR Localization/Translation
I'm from inlang and we have a fully configurable JavaScript i18n library with paraglide-js that might help you. There will be a dedicated adapter of the library for NextJS that is more integrated into the framework. Until then you can look at our NextJS example and set the library up this way.
-
Internationalization best practices for front-end developers
i am on a 2 year long rabbit hole to solve many i18n problems that devs face https://github.com/inlang/inlang
we are in our third (major) refactor because the problem is so complex and new requirements emerge regularly :/
-
Suggest Best Svelte Libraries
inlang: localization infrastructure for software and the next git (made by the inlang team and same author of the amazing typesafe-i18n library)
-
Using ChatGPT to auto generate config files: Wasted effort for us
https://www.loom.com/share/85d77004aa4c4bea9752d959c229e577
The irony is that this is not needed anymore. The plugin API simplified the config interface so much that initializing configs only differs by the used plugins and their respective configs.
The only useful thing that chatgpt provides is deriving what files in a filesystem are translation files. But a hardcoded version might be faster and more resilient.
Learning: The GPT hype is ... well hype. The amount of work that went into this feature is insane. The work boils down to software engineering. Sure, tools will emerge that make prompt engineering easier but so does the previous ML hypetrain led to endless nocode machine learning tools. Yet, there is no "disruptive everyone builds ML models" (for GPT "everyone will become a developer") nocode machine learning tool in sight. Maybe signaling that the premise of ML NoCode/GPT of "this works for everything" is not true. Deriving what files are translation files, yep. Deriving an entire config file, maybe not.
[0] https://github.com/inlang/inlang/discussions/408#discussion-4914727
-
I created a vscode extension that can automatically add translation keys to your html
We faced the same issue and build a viscose extension too! https://github.com/inlang/inlang/tree/main/source-code/ide-extension
What are some alternatives?
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
typesafe-i18n - A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects.
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
nextjs-monorepo-example - Collection of monorepo tips & tricks
i18next - i18next: learn once - translate everywhere
firefly - The official IOTA and Shimmer wallet
surveys - YAML config files for the Devographics surveys
next-i18next - The easiest way to translate your NextJs apps.
tolgee-platform - Developer & translator friendly web-based localization platform
svelte-i18n - Internationalization library for Svelte
astro - The web framework for content-driven websites. βοΈ Star to support our work!