Pinned Tweet
Just released v1.1.0 of cli-forge, a modern CLI builder for node JS built to deal with some frustrations we hit with yargs while working on Nx.
github.com/AgentEnder/cli-fo…
This release features:
- builtin localization
- llms.txt generation
- strict mode
Super happy w/ the dynamic opengraph on npm-burst
npm-burst.com/package/nx/
Craigory Coppola retweeted
Monorepo tooling enable fast and efficient CI. It doesn't always feel this way, but at that scale, CI simply wouldn't run without proper tooling.
The catch: splitting code into thousands of units and rethinking how everyone works. A huge upfront investment, even with agents.
Craigory Coppola retweeted
On Oct 22, we’re hosting a free online event on the future of CI. We'll share our biggest updates in years.
It feels like I haven't slept in a long time to make this happen :) Really excited to share what we have.
Register: nx.dev/events/2026-oct-produ…
#monorepos @NxDevTools
Moved npm-burst.com/ 's charts over to @tan_stack charts now that it is v1, much much nicer than the manual d3 charts it was on before.
Very happy with how claude was able to reason through the library too.
Thanks for the assist with the video @juristr! I love how this setup works out and immediately points to issues when things fall out of sync
Full end to end type safety achieved 🎉
- C#/.NET backend
- React + TypeScript frontend
Change something in the backend API and frontend type checking fails immediately.
@juristr walks through how to set this up in an Nx monorepo.
Craigory Coppola retweeted
IMO CI should be something you set up once and then you forget. It should autoscale, adapt to project/workspace changes etc.
What’s your main issue👇
Craigory Coppola retweeted
🚀 Nx 23.2 is out.
- Oxlint & Oxfmt
- Leaner CLI output for AI agents and CI
- Caching across local clones & agent sandboxes
- TUI status bar and VIM search
- @angular 22.1
- Expanded @vitest_dev support
And more. All the details 👇
nx.dev/blog/nx-23-2-release
This blog post has been a long time coming, it distills a talk I've given at a few conferences into an easy to follow guide for full stack type safety.
Full end-to-end type safety across tech stacks is a dream for many developers. @EnderAgent makes it look easy.
In his latest article, he shows how to achieve full-stack type safety in an Nx monorepo hosting a .NET WebAPI with a JavaScript frontend.
nx.dev/blog/dotnet-openapi-t…
I've been working through some genealogy research recently, and I've come to the conclusion that at some point unless I reach a celeb... I could care less what the names are.
I want to know more about **who** they were, and less about the facts most research sites help with.
Oh fancy! I just learned a new @trypolygraph command to help clean up worktrees that have accumulated throughout a dev cycle...
`polygraph session prune` works through and finds those lingering bits to clean up. A bit like npkill but for full worktrees.
Craigory Coppola retweeted
Lots of new GitHub competitors and products emerging trying to take advantage of GitHub being hugged to death.
And yet, nearly every single one misses the point: GitHub is an incredible product
a) GitHub gives away a ridiculous amount of compute and storage for free - GitHub actions, cache, packages, release artifacts, pages, etc etc etc - tons of value immediately usable
b) its ridiculously easy to sign up, push some code, make an action, store some stuff, and get up and going with one “git push” command - no one has the time or energy to integrate 13 new workflows and tools (this is why jj never took off and why I suspect something like tangled’s nix runners won’t be popular)
c) unfortunately, for better or for worst, unless these things result in a superior product, implementation and architecture do not matter. No one REALLY cares if your product is backed by intergalactic-interconnected-durable-objects in space: they care if it solves a problem, they get good value from using it, and it’s usable.
Yes GitHub availability is shit these days. I hope it gets better: not because I hope they figure out how to scale their networks and HAproxy and compute to the moon. I hope it gets better because it’s an amazing product with incredible value that I enjoy using. Nothing else compares.
Craigory Coppola retweeted
My @WeAreDevs talk
Meta Harnesses: What the JS Framework Wars Teach Us About What Is Next for AI Agents
is online:
wearedevelopers.com/videos/1…
@trypolygraph #metaharness
Hello 👋, I'm looking to chat with anyone that's picked up the new `@nx/dotnet` plugin, or anyone that is still using the community `@nx-dotnet/core` plugin.
Feel free to reach out via DMs or drop a reply here, mainly looking to understand gaps.
Replying to @NxDevTools
Nx .NET is now GA in Nx 23. Run .NET straight in an Nx workspace, no special scaffolding.
It uses MSBuild to infer targets, and caches build/test/publish/pack.
<ProjectReference> links wire into the graph, so nx affected and nx graph work.
One task graph across stacks.
Heads up, this doesn't appear to reset to your default model when running /clear, so its not exactly per-session. I've ran through a bit more fable quota than I care to admit because of this 😅
Just in time! I've been playing around with herdr a ton the past week or so, its been a pleasure. @trypolygraph
integration can only make things better.
Just implemented this: @trypolygraph can now fully leverage @herdrdev by automatically spawning and coordinating agents in Herdr panes for changes that span multiple repos.
Herd away! 🐏
ICYMI, there's a tracking issue for the typescript 7.1 APIs now: github.com/microsoft/typescr…













