dictionary
nx


dictionary | nx | |
---|---|---|
1 | 364 | |
37 | 24,528 | |
- | 2.0% | |
6.0 | 10.0 | |
over 1 year ago | 3 days ago | |
TypeScript | TypeScript | |
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.
dictionary
-
Helpful content when memorizing English words
Project URL: https://cihat.github.io/dictionary/ Source Code: https://github.com/cihat/dictionary
nx
-
CodeMash 2025
Nx (sponsored the Lightning Talks)
-
I'll think twice before using GitHub Actions again
Caching and sharing artifacts is usually the main culprit. My company has been using https://nx.dev/ for that. It works locally as well and CI and it just works.
Our NX is pointed to store artifacts in GHA, but our GHA scripts don't do any caching directly, it is all handled by NX. It works so well I would even consider pulling a nodejs environment to run it in non-nodejs projects (although I haven't tried, probably would run into some problems).
It is somewhat heavy on configuration, but it just moves the complexity from CI configuration to NX configuration (which is nicer IMO). Our CI pipelines are super fast if you don't hit one of one of our slow compilling parts of the codebase.
It is quite interesting is that your local dev environment can pull the cached items there were build from previous CI ran-jobs or other devs. We have some native C++ dependencies that are kind of a pain to build locally, our dev machines can pull the built binaries built by other devs (since all devs and CI also share the same cache-artifacts storage). So it makes developing locally a lot easier as well, I don't even remember last time I had to build the native C++ stuff myself since I don't work on it.
-
Custom builder for Angular: My way
An efficient work environment is the key to rapid development and testing. Many of us have heard stories about how it takes days or even weeks to set up a work environment at a new job or project. I am not exception! To avoid such situations, I decided to think through the structure and configuration in advance. The main idea was to make everything reproducible and easy to use. Since the goal was to develop a plugin for nx.dev, I started by creating a new workspace via create-nx-workspace. I used the test application to experiment with SSR, and therefore created a plugin template using @nx/plugin:plugin. Additionally, I generated two applications and one library via NX generators. As a result, the project structure looked like this:
-
Monorepo and Micro-Frontends Using Module Federation + Vite
Nx Documentation Vite Documentation Webpack Module Federation Micro-Frontend Architecture
-
We switched from Next.js to Astro (and why it might interest you)
Just use react.... That's what I do - it is so much easier than trying to fight with Next.js.
I have a large application and I use next.js for the landing pages (landing, tos, privacy, blog, login, etc..) - but for the core application after login, I just use vanilla react with react router. For me I keep these as separate applications as I don't want to load the entire app just for the landing page or login box.
Every time I need to work in the nextjs part of the app I always run into problems and have to read the docs and troubleshoot, sift through which part of the docs apply to my setup versus the app router.
If your entire application needs to be indexed as a static site (e.g. content based versus a web application), then vanilla react isn't a good fit - so it depends on your needs.
Unrelated - but shout out to https://nx.dev. I always prefer using this for all of my projects - made it super easy to have my node backend, react frontend, nextjs landing page, chrome extension, cron jobs, etc.. all in the same codebase where I can share code between all of them via non-publishable libraries.
-
A Practical guide to building cross-platform apps with Angular, Ionic, Capacitor, and Nx
Nx Documentation
-
Nx 20: Exploring the new TS preset and TypeScript project references
However, the potential for future improvements make it a promising approach for large-scale monorepos. As the Nx team works on supporting TypeScript better (see Nx 2025 roadmap), we can expect progress in this area.
- Nx Powerpack Moves Previously Free Feature Behind Paywall
-
Why You Should TRUST Frameworks (And What It Takes to Build One From Scratch)
Finally, NX allows us to extend its capabilities with custom plugins and generators to automate workflows, create boilerplates, and manage continuous migrations. This helps developers evolve the codebase over time with minimal effort as new features are introduced or technologies change.
-
AnalogJS 🤝 Zerops: Official Deployment Partners
Analog is excited to have Zerops as our new official deployment partner. We are thankful for the trust and support of the entire Zerops team. Because of their support, in addition to our other sponsors, SnyderTech, Jonathan Gamble, and Nx that we are able to receive ongoing maintenance and keep developing Analog for the long term in a financially sustainable way.
What are some alternatives?
buefy - Lightweight UI components for Vue.js based on Bulma
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
cleasby-vigfusson-next - The Cleasby & Vigfusson Old Norse Dictionary for Next.js
single-spa - The router for easy microfrontends
sst - Build full-stack apps on your own infrastructure.
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
sharp-collections - TypeScript LINQ library implementing all .NET LINQ methods and some more.
lerna - Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Medusa - The world's most flexible commerce platform.
Bit - A build system for development of composable software.
Refine - A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
create-react-app - Set up a modern web app by running one command.

