![]() While having pnpm manage the node version is a noble mission, it seems that the existence of the (what should be optional) feature is somehow making things more complex instead of less. ![]() To fix this issue, install the required Node version.Īlso running into something like this when trying to have pnpm coexist with volta. This is happening because the package's manifest has an engines.node field specified. Your Node version is incompatible with version: >=16.9 Lockfile is up to date, resolution step is skippedĮRR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version) Progress: resolved 190, reused 169, downloaded 0, added 169, done Install community-maintained integrations:ģ: git init & git add -A & git commit -m "Initial commit" (optional) √ Add type checking with TypeScript? » Yes, using JavaScript with JSDoc comments √ Which Svelte app template? » SvelteKit demo app Problems? Open an issue on if none exists already. This is beta software expect bugs and missing features. ![]() ![]() /.pnpm-store/v3/tmp/dlx-18352 | Progress: resolved 5, reused 5, downloaded 0, added 5, done Packages are hard linked from the content-addressable store to the virtual store.Ĭontent-addressable store is at: D:\.pnpm-store\v3 Λ Invoke-WebRequest -OutFile pnpm-win-圆4.exe ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |