Sabitlenmiş Tweet
jdx
552 posts

jdx
@jdxcode
I make dev tools. I love CLIs. https://t.co/VVNmJX4LVt
Dallas, TX Katılım Temmuz 2006
1.2K Takip Edilen2.9K Takipçiler

@neogoose_btw I’m not sure I mind when my users do this. I think hearing what an agent has to say is often a lot more useful to me than an (understandably) clueless user
English

And we are now full on aube from pnpm
github.com/tuist/tuist/pu…
English

@nateberkopec this seems to be the consensus! I'm glad I asked because it's not what I expected
English

@jdxcode idk man especially these days where I can be like “hey Claude just mirror all my package json tasks in Mise” it’s not a huge bonus
English

@jdxcode Because just supports subdirectory tasks, unless I’m missing that feature in mise?
English

@jdxcode How about using just that? That’s what I’m currently using, but I’d be happy to switch it out for mise.
English

@davidlormor Yeah, I think plugins may be the right answer here. mise can provide the task layer, while a Rails/Pitchfork plugin could auto-define the obvious project tasks instead of making every app hand-write the same glue.
English

@jdxcode I’ve been pondering this lately - I’ve got a “monorepo” that’s a mix of TypeScript, Ruby, Terraform, etc. (it’s a Rails app…). Mise/Pitchfork would be great for a unified interface for dev environments, but I’m still tinkering with the best way to handle it…
English

@rob_ferney Totally fair to prefer ecosystem task runners, but tasks have been a core feature in mise since 2023 and a lot of users really like them.
English

@jdxcode If anything, Making a second utility that mise can install to handle tasks could be a thing..
sous as a name comes to mind if you want to keep with the cooking theme 😀
English

@rob_ferney this sounds more like you don't think mise should have tasks at all?
English

@jdxcode Clean separation of concerns. Mise does its job very well!
Let the apps that mise manages do the tasks.
English

Let's move @tuistdev to Aube. Betting on @jdxcode's work is always an investment with great long-term dividends
github.com/tuist/tuist/pu…
English

@anthonysheww cheat away! I'm sure I took some turborepo ideas and made it part of mise tasks—this is how users get great products!
English

@jdxcode Just reading about aube now - very cool! Was looking to put this exact same behavior into Turborepo, so glad to have some notes to cheat off of. 😄
English

Aube doesn’t have a guide on worktrees because its default behavior is already ideal for worktrees
Anthony Shew@anthonysheww
Check out how @pnpmjs solves npm dependencies for Git worktrees with zero configuration. pnpm.io/next/git-workt…
English

@jdxcode The pnpm guide is describing the default behavior. It’s explaining that behavior in the context of worktrees to be helpful for users who don’t immediately make the connection. 😄
English

@jackmorrison @colinarms @conductor_build @endevinc yes, it uses a global virtual store out of the box so each worktree just contains a pile of symlinks. No other node package manager offers this out of the box.
English

I somehow ended up with 1TB worth of node_modules in my @conductor_build git worktree folders because every fresh worktree does a `yarn install`
What's the solution here? Yarn hardlinks, yarn PnP, move to pnpm, etc?

English

I think I need to get the world onto github.com/suzuki-shunsuk…
Long-lived gh tokens with agentic workflows should be like running your services over http.
English

This is how I am with PRs. My slop is fine, idk how y'all end up with all that slap.
Earth_Wanderer@earth_tracker
Marriage in 31 seconds: wife auditioning oranges for the Olympics, husband already accepted his fate. 😂
English







