Eric Clemmons 🍊☁️

Been entirely hand-coding during my break and GitButler still fits my workflow best. Basically, make a bunch of changes until work is actually done (“Split ThisAgent into Y&Z”, “Add Router”, “Enable OAuth”)

@youyuxi @branchseer In that case, it seems like the best usage is `vp run build` and `vp run checks` etc. just-in-case `vp build` has a dependency to work. TBH, I was kinda hoping that `vp check|test|build` was going to be ubiquitous across projects. But I'll need to have `run.*` equivalents...

@ericclemmons @branchseer Instead - always "vp run xxx"

One thing that I know some people will complain about, and @theo did in fact complained about, is how ‘vp dev’ is a built-in command rather than running the dev script like a package manager does. Fundamentally this is because vp is not a package manager or just a task runner - it’s a full toolchain. A package manager doesn’t have a built-in dev feature, but vp does. Running scripts is something vp can do, but you make the intention explicit via ‘vp run’ instead of expecting implicit fallback. I actually very much dislike the implicit script fallback behavior because it forces you to remember what built-in commands the runner has - for example, you can’t run a script named ‘deploy’ with ’pnpm deploy’ because… turns out pnpm has a built-in deploy command. With the large command surface vp has, implicit fallback is only going to be confusing than helpful.

@BraydenWilmoth What a great domain too

Vector search emails with natural language! Crazy how much of the Cloudflare stack this service is using. DO, D1, KV, Workers, Vectorize, Turnstile, R2, Workers AI, Gateway + more. By far the best though... Dynamic Worker Loaders. AI generates code and runs it in a secure sandbox INSIDE my existing Worker without needing an actual VM sandbox. More public access next week – small test group is stress testing it right now :)

@branchseer @youyuxi So I can or cannot have a dependsOn for “vp build”? That’s what I was trying to accomplish – make the top-level commands remove the need for custom bespoke tasks the team needs to remember. Always vp dev. Always vp check. Always vp build.

@youyuxi @ericclemmons Your screenshots show that `dependsOn` works in `vp run dev` but not in `vp dev`. That's by design: the `run` config doesn't affect any non-run Vite+ subcommands. The principle is that each top-level field in `vite.config.ts` only affects the vite+ subcommand with the same name.

@youyuxi I must be doing something obviously wrong. Tested it again and `vp dev` doesn't run dependsOn?

@ericclemmons @theo It is supported! You just need to configure it under run.tasks in vite config

@jherr Happy for you Jack!

Really excited to join the @Netlify team and ship amazing AI and full stack features!

Agents have me calling setState again, which means its time to bust out immerjs.github.io/immer/

@youyuxi @theo I think that's fair for scripts (`vp run deploy`), but should `dependsOn` at least be supported? For `check`, `dev`, & `build`, the need an updated `wrangler types`. I have that in `prepare` now as a side-effect of `vp install`, but this looks so clean: #github-actions" target="_blank" rel="nofollow noopener">viteplus.dev/guide/ci#githu…

@theo Also the mindset is “vp xxx” is always a built-in command and will never run your scripts. Only “vp run xxx” runs your scripts. No room for confusion IMO, just a habit problem.

@ddunderfelt Went from “I have a few nits” to “lgtm!”

Finally got a pretty good pfp result with Nano Banana 2. For reference, the second pic is one I took in 2021, and I've never liked how serious I look in it. Also, I have glasses now and have lost weight, so the AI edit is what I actually look like now. I should also take a completely new pfp but this will do for now.

@vinicius_dacal Maybe? I think test cases capture behavior and “what” it does. The “why” (or “why not”) decision is more like “would prefer this API, but cannot use it due to Y constraints, so we have to compensate by comparing X to Z”

@ericclemmons Honest question: couldn’t that be expressed as a test case?

I’m at the point that I want to add: // why this next line uses this function // instead of something else to most of my code I don’t see the sense of burying that valuable of information behind a PR review. (Every PR review should become a code comment?)

@dillon_mulroy @J_Kreutzbender Adding this to my codebase today (try/catch seems like a smell now) Was going all in on Effect-smol, but will probably wait for docs to land since I’m so slow with it today

@J_Kreutzbender if you can't go all in on effect here you could clean this up w/ better-result (npm i better-result) github.com/dmmulroy/bette…

I hate everything about this. Desperate for Effect chaining here

i don't know if it's possible for an article to have *too much* good information in it, but i'd like to present this one as a candidate.

@wesbos The only thing that I had to get used to is “vp run dev” to make sure the task dependencies ran. “pnpm dev” is muscle memory

Vite+ is SO GOOD I’ve moved 3 sites over and scaffolded out a few more. So sold

Every. Single. Time.

@zebassembly Happy birthday!🎈

Today is my birthday and now I'm halfway through my 20s, wtf

If you’re moving faster with AI, but not seeing quality and delivery on the other end, give this a read. The anecdote on QA and trust hits home.

@voidzerodev lol this is how I felt after switching over. I don't even run `pnpm` anymore – just `vp add/remove` x.com/ericclemmons/s…

Let it be the last switch then! No pressure to do it now (or at all, because your agent can do it for you as well).

Having syntax errors with Agents' @⁠callable & Vite 8? oxc doesn't support TC39 decorators yet, so you need to follow these instructions: #javascript-transforms-by-oxc" target="_blank" rel="nofollow noopener">main.vite.dev/guide/migratio… Not sure if #syntaxerror-invalid-or-unexpected-token" target="_blank" rel="nofollow noopener">developers.cloudflare.com/agents/api-ref… should include this yet?

When it comes to @threepointone, there’s no need to assume good intent. It’s always good.