monorepo
nextjs-monorepo-example
monorepo | nextjs-monorepo-example | |
---|---|---|
56 | 19 | |
962 | 1,465 | |
4.1% | - | |
10.0 | 9.9 | |
5 days ago | 6 days ago | |
TypeScript | 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.
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
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?
typesafe-i18n - A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects.
next-i18next - The easiest way to translate your NextJs apps.
firefly - The official IOTA and Shimmer wallet
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components
surveys - YAML config files for the Devographics surveys
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
tolgee-platform - Developer & translator friendly web-based localization platform
nextron - ⚡ Next.js + Electron ⚡
astro - The web framework for content-driven websites. ⭐️ Star to support our work!