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.
https://t.co/ZqrN2Uc1hP
This release features:
- builtin localization
- llms.txt generation
- strict mode
Is this something people actually want? I dislike the whole test colocation thing in rust, and in .NET its a whole separate project.
JS tests in their own `.spec.ts` files seems like a happy middle ground to me.
❓Did you know you can write “in-source tests” in JavaScript
Rstest supports in-source tests — write your test right next to the code. Test code is stripped in production builds. Zero bundle cost. ⚡️
Rust-style DX, now in your JS toolchain 🦀
#JavaScript#Rstest#Rspack
Really excited to see that the official nx/dotnet plugin has surpassed the original community plugin in weekly downloads now.
Combining the two that's 54k weekly downloads for using .NET in an @nxdevtools repo, crazy to think that this is just the beginning.
Consumed this programmatically and threw up a small static site so its easier to consume on mobile when working with AI agents through their apps/web interfaces
https://t.co/bMXlfqopD9
I'm not going to say its "the best way" or anything like that, but I published a small script that uses gh cli to "digest" the state of a PR to feed into an LLM: https://t.co/ORoR8pIa9S
This was born out of frustration with Claude invoking the gh CLI more times than necessary.
@ScriptedAlchemy@boshen_c I feel this came off a bit harsh, its not meant to be snide or anything - just showing the "support as a runtime" does have overhead where you need to create + track issues that are runtime specific even if you don't plan for it.
@ScriptedAlchemy@boshen_c Thats definitely supposed to be the case... but this one's been in needs triage for 2 months now: https://t.co/ghRX5MwbQh
Deno fixed the same thing in about a weeks time.
I'm not going to say its "the best way" or anything like that, but I published a small script that uses gh cli to "digest" the state of a PR to feed into an LLM: https://t.co/ORoR8pIa9S
This was born out of frustration with Claude invoking the gh CLI more times than necessary.
This uses the current patch diff for the PR, the timeline of the changes that have been applied, comments (and whether they are already resolved or not) to create markdown outputs suitable to feed into claude/codex/etc for updating post PR review
@chux13786509@NotBatmanDev This feels like a bit of a cop out no? There's no guarantee the secrets going to be in git history. I was looking for something that was 100% incorrect, not just a "maybe". There's not anything directly wrong with using process.env here either?
@juristr Ah, the single executable bit with bun is indeed nice. I've not played with bun + cli-forge tbh, but I think things should still work fine.
None of its setup involves file-based routes or things like that, so the bundling itself shouldn't kill it.
@juristr Docs site isn't the prettiest, but I'm pretty sure its the best way to write type-safe CLIs in typescript. Super extensible, its honestly one of the projects I'm more proud of.
https://t.co/aMAX340mpl
@juristr Oh, if you are doing this cli-forge offers a way to generate llms md files from your cli and auto generates help. Should be a natural pairing.
I wonder how hard it would be to have it write skills too