fluent.js
nextjs-monorepo-example
Our great sponsors
fluent.js | nextjs-monorepo-example | |
---|---|---|
18 | 19 | |
893 | 1,465 | |
1.5% | - | |
6.7 | 9.9 | |
26 days ago | 3 days ago | |
JavaScript | TypeScript | |
Apache License 2.0 | 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.
fluent.js
-
Internationalize TypeScript app
Want to quick internationalize your app? You can use com.hydroper.ftl from NPM, which uses Fluent. Should work for browser (if you use Webpack targetting "browser") and NodeJS. It uses Intl from ECMA-402 and @fluent/bundle.
-
FTL loader
Fluent is a localization system with more flexibility for translators. FTL means to Fluent Translation List. It seems to refer to the syntax used to define resources, which are (roughly) collections of messages.
- Requesting feedback on a string interpolation concept
-
Questions about a translation system
In general though, translation is very hard. There are more exceptions than rules, and a lot of work has gone into the libraries to support all languages. consider using something like https://projectfluent.org/ if this isn't just a learning exercise.
-
l10n: A proc macros crate to ease project localization and provide compile time checks (message exists, mandatory arguments are set, functions are defined) built upon fluent-bundle.
Working on a personal project that needed localization I decided to use fluent from Mozilla. It already exists an excellent crate to use fluent in Rust which is fluent-bundle (and others fluent crates) but now that I'm used to "If it compiles, it works" I wanted to have a macro that checked that the "localization messages" I'm using existed and had all the required arguments, not finding what I was looking for I decided to write this crate for my needs and share it with the community.
-
Are there any C++ libraries that provide tools for composing English language sentences?
Even if you're not planning to translate your game into other languages, it might be worth looking into one of the localisation systems. For example, Mozilla's Fluent handles pluralisation, gender, etc..
-
Show HN: Localization and translations should be code, not data
It's a tempting argument. By interviewing hundreds of people a different pattern emerged though. Translators don't know how to code. Some companies manually removed quotation marks (") from strings because they confused translators.
What do you think about Mozilla's Fluent format/syntax https://projectfluent.org/?
BTW feel free to reach out via email to me. Look at my profile to find it.
-
I18N in the Multiverse of Formats
The last format in this multiverse trip is Fluent a Mozilla project. The Fluent format shares a lot of philosophy that drove the design of ICU Message Format.
-
Travelm-Agency Updates (Fluent, Webpack)
My Elm code generator for i18n files Travelm-Agency has just reached a critical milestone: supporting all of projectfluents constructs. Yes, that means even locale specific constructs like matching on PluralRules (zero, one, few, many, other) or formatting dates and numbers based on the current locale! As far as I'm aware that is something that no other i18n solution for Elm can do so far.
-
Unsoundness in owning_ref
As an example, there is a really good localisation framework called Project Fluent where you write your translatable expressions in a text file that later gets parsed. The resulting parse tree borrows entirely from the original text and doesn't make any allocations other than the occasional Vec for sequences.
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).
What are some alternatives?
i18n-js - It's a small library to provide the I18n translations on the Javascript. It comes with Rails support.
next-i18next - The easiest way to translate your NextJs apps.
react-intl-example - React internationalization with react-intl
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
pseudo-localization - Dynamic pseudo-localization in the browser and nodejs
serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components
rails-i18n - Repository for collecting Locale data for Ruby on Rails I18n as well as other interesting, Rails related I18n stuff
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
nextron - ⚡ Next.js + Electron ⚡
monorepo - globalization ecosystem && change control SDK