Environment hell, inverted.
Install · Usage · Release Channels
Experimental 0.x: EnvHeaven is currently in experimental
0.xdevelopment. APIs, CLI commands, plugin contracts, package names, and release behavior may change before1.0.0. Pin versions and read release notes before using it in production workflows.
| Channel | Install | Purpose |
|---|---|---|
release |
npm install @envheaven/plugins-nodejs-pnpm@release |
recommended 0.x release track |
latest |
npm install @envheaven/plugins-nodejs-pnpm |
npm default alias for the release track |
exp |
npm install @envheaven/plugins-nodejs-pnpm@exp |
experimental builds with newer changes |
Install compatible envheaven host package in the same workflow.
Run pnpm scripts and local pnpm exec binaries through EnvHeaven.
pnpm-runfor package scripts.pnpm-execfor local CLI binaries.- readiness diagnostics before execution.
- structured process execution through the plugin host.
Node.js >=20, EnvHeaven host package, pnpm, and a target package.json.
| Channel | Install | Purpose |
|---|---|---|
release |
npm install @envheaven/plugins-nodejs-pnpm@release |
recommended 0.x release track |
latest |
npm install @envheaven/plugins-nodejs-pnpm |
npm default alias for the release track |
exp |
npm install @envheaven/plugins-nodejs-pnpm@exp |
experimental builds with newer changes |
release is the recommended 0.x track, not a stable API promise.
Experimental. Plugin contracts may change before EnvHeaven 1.0.0.
MIT, as declared in package.json.
{ "pluginPackage": "@envheaven/plugins-nodejs-pnpm", "Execution": { "cwd": "." } }