reamplify
nx
reamplify | nx | |
---|---|---|
3 | 346 | |
16 | 22,004 | |
- | 1.5% | |
0.0 | 10.0 | |
almost 2 years ago | 1 day ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
reamplify
-
Monorepos in JavaScript and TypeScript
My experience was very similar: I built an application using a GraphQL schema file that powered AppSync templated VTL/DynamoDB tables, as well as automatically generating GraphQL operations/types. When I cleaned up the application's template for reuse, I erroneously decided to try out Yarn 3/Lerna/PnP, and then lost an embarrassingly long time to make it work.
Each [1] tool [2] seemed [3] to break differently, and needed some form of manual massaging to make it work. That manual massaging meant learning a new configuration file syntax, multiple times.
When it worked, it felt magical. Weaving together an entire web app, powered by a small bit of GraphQL schema [4] means building at a high level of abstraction (hence can be very productive). The only issue is the muddy forest of the NPM ecosystem you're surrounded by: any step towards upgrading your external dependencies seems to cost far more time than promised.
[1] Yarn3/PnP seems to assume all packages define their dependencies correctly. Unfortunately, this isn't true in the real world. I spent hours massaging dependencies in https://github.com/ThomasRooney/reamplify/blob/master/.yarnr...
- Newsletter martinmueller.dev 2022 week 19
- I just open-sourced my start-up's infrastructure as a starter kit: Yarn 3/PnP/CDK/React 18/AppSync/DynamoDB with CI/CD, Monitoring, Slack Alerts, Backup/Restore built-in
nx
-
🍒 Cherry-Picked Nx v18.3 Updates
One notable feature is the ability to remember selected tabs. When you select a specific tab on a page, all other tabs on the page with the same name will also be selected. This selection will persist during your next visit to nx.dev.
-
Pitfalls of Deploying Hono Js App on Vercel
Hono does have a template application for Vercel, but in my case, my requirements were different (aren't they always 😅). I was working in a monorepo (using nx) because I wanted to manage my libs, tests, and examples all together in a single place, instead of having different repos.
- 🍒 Cherry-Picked Nx v18.1 Updates
-
How to setup semantic release with GitHub Actions.
Recently, My coworker is using Nx to automate his workflow, including automated release using semantic version. I found this method quite useful, so I want to re-implement on single GitHub repositories (without Nx).
-
🩹 Nx Crystal Plugin Picking the Essentials
I started a discussion on GitHub concerning that subject: Design Nx Plugin Project Crystal
-
Things I learned while building projects with NX
Nx
- Episode 24/09: Testing without TestBed, SSR & Hydration
-
Announcing AnalogJS 1.0 🚀
We are looking for companies to partner with on the Analog project to support development of the project. Thanks to Snyder Technologies for being an early adopter and promoter of Analog, Nx for joining us as a sponsor, House of Angular, and many other backers of the project.
-
Storybook 8
Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.
-
⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.
What are some alternatives?
wireit - Wireit upgrades your npm/pnpm/yarn scripts to make them smarter and more efficient.
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]
amplify-spiders-v1 - A tool for search engine based competitive analysis. AWS Amplify project with many web crawlers for different search engines, and a simple web frontend for displaying historical results in Next.js
single-spa - The router for easy microfrontends
senjuns - Monorepo for wiki, landingpage, AWS CDK code and more for Senjuns. Senjuns is (will be) a freelancer platform for connecting seniors and juniors with clients.
vite - Next generation frontend tooling. It's fast!
devkit-io nextjs amplify starter kit - CDK Next.js Amplify Starter Kit for AWS
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
create-react-app - Set up a modern web app by running one command.
pnpm - Fast, disk space efficient package manager
Bazel - a fast, scalable, multi-language and extensible build system
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos