OSS activity in April 2026

About one month after I sent my first PR in March, I was invited to the Vite+ Core Team. After that, I also started to reproduce Issues and review PRs, not only my own PRs.

voidzero-dev/vite-plus

feat(env): add Nushell support via env.nu wrapper (#1312)

I made vp env work with Nushell too (#1144). Work on full Nushell support was in progress in #1305. That change was large. So this PR covers only vp env, as the Issue says.

Before this, I had never written Rust in a product. So I read the code while an AI explained how to read it. I tested the changes in a real Nushell. I also found these facts while I worked. In Nushell, source resolves the path at parse time. So a path that uses $HOME fails. You must write the path from ~, for example ~/.vite-plus/env.nu.

feat(migrate/create): add TypeScript shim for Vue and Astro component files (#1411)

vp create and vp migrate now add a type shim to Vue and Astro projects (#1278). For Vue, the shim writes a declare module for *.vue to env.d.ts. For Astro, it writes a reference to astro/client to env.d.ts. So vp check does not show type errors in a project you just created.

docs: add Zed integration details to IDE documentation (#1455)

I added the settings for using Vite+ with Zed to the IDE documentation (#826).

fix: add vite-plus/pack/client export as tsdown/client equivalent (#1501)

In projects that moved from tsdown, a reference to tsdown/client gave a type error. Vite+ had no equivalent export (#1500). So I added vite-plus/pack/client. I split the rewrite of the references into two PRs in May, #1541 and #1542. The three PRs were merged together on May 11.