Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

PowerShell `vp` wrapper hides failures: `$?` is `True` and `&&` keeps going after `vp` fails

Closed Beginner friendly
  • Is something wrong?
#2,934 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@fengmk2 is already working on this.

Since Oct 8, 2026.

  • #2947 by @fengmk2 — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
powershell, rust, typescript
Domain
cli

Research direction

Start by reading the vp function in env.ps1 and compare its PowerShell status behavior with running vp.exe directly. Reproduce the failure with a command that makes vp pack fail, then check $LASTEXITCODE, $?, and an && chain. Done when the wrapper reports failure through $? and prevents the chain from continuing.

Written by the indexing model from the issue text.

Description

bug pending triage
Describe the bug

In PowerShell, the vp function defined in env.ps1 loses the exit status of the vp.exe binary. When a command fails, $LASTEXITCODE is set correctly, but $? is True.

Reproduction

see below

Steps to reproduce

example vite.config.ts:

export default defineConfig({
  pack: {
    entry: 'src/does-not-exist.js'
  },
});

In powershell:

> vp pack
VITE+ - The Unified Toolchain for the Web

ℹ entry: src/does-not-exist.js
...
error: Build failed with 1 error:

[UNRESOLVED_ENTRY] Cannot resolve entry module src/fail.js.

    at ...

> "$LastExitCode $?"
1 True

vp pack returns with exit code 1 (good), and with status True (bad).

running vp.exe directly does not have this issue:

> vp.exe pack           
VITE+ - The Unified Toolchain for the Web

ℹ entry: src/does-not-exist.js
...
error: Build failed with 1 error:

[UNRESOLVED_ENTRY] Cannot resolve entry module src/fail.js.

    at ...

> "$LastExitCode $?"    
1 False

with vp.exe, $? correctly outputs False, which correctly breaks && chains for example

System Info
> vp env current
VITE+ - The Unified Toolchain for the Web

Node.js:
  Version    26.11.0
  Source     devEngines.runtime
  Bin Path   C:\Users\me\AppData\Local\vite-plus\data\js_runtime\node\26.11.0\node.exe
  Installed  true
  Mode       managed

Package Manager:
  Name       npm
  Version    12.2.0
  Source     devEngines.packageManager
  Bin Paths  
    npm      C:\Users\me\AppData\Local\vite-plus\data\package_manager\npm\12.2.0\npm\bin\npm.cmd
    npx      C:\Users\me\AppData\Local\vite-plus\data\package_manager\npm\12.2.0\npm\bin\npx.cmd
  Installed  true
  Mode       managed

> vp --version  
VITE+ - The Unified Toolchain for the Web

vp v1.1.0

Local vite-plus:
  vite-plus  v1.1.0

Tools:
  vite             v8.3.3
  rolldown         v1.2.12
  vitest           v5.0.3
  oxfmt            v0.72.0
  oxlint           v1.87.0
  oxlint-tsgolint  v7.0.2003
  tsdown           v0.23.0

Environment:
  Package manager  npm ^12.2.0
  Node.js          v26.11.0 (devEngines.runtime)
Used Package Manager

npm

Logs
Validations
Dominant language
Rust
Stars
6k
Forks
274
Avg merge
1d 11h
Merged PRs (30d)
206

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.