Zoltan Kochan comments

Results 827 comments of


                                            Zoltan Kochan

Windows Execution Policy error `pnpm.ps1` is not digitally signed

We'll have to look into it. As far as I remember, we don't create the ps1 shims specifically because of this issue. So, maybe corepack created it? Not sure.

`#` character when installing from Git is incompatible with Vite

> It is not valid for an npm package name to contain # ([source](https://www.npmjs.com/package/validate-npm-package-name)), but when you install from git it writes a package to the file system using #...

`#` character when installing from Git is incompatible with Vite

Fixed in v10

fix: git-resolver overhaul

Why have you closed it?

ERROR Cannot read property 'optionalDependencies' of undefined

Could you create a sample repository that reproduce this?

Can't upgrade pnpm version: EPERM: operation not permitted, unlink `AppData\Local\pnpm\pnpm.EXE`

Have you tried to run your terminal with admin permissions?

Can't upgrade pnpm version: EPERM: operation not permitted, unlink `AppData\Local\pnpm\pnpm.EXE`

Does the standalone script work to reinstall pnpm? https://pnpm.io/installation#on-windows

Can't upgrade pnpm version: EPERM: operation not permitted, unlink `AppData\Local\pnpm\pnpm.EXE`

I think `pnpm add -g @pnpm/exe` should also be fixed. But use this upgrade method for now.

bin from optional dependencies of a devDependencies are not linked in node_modules/.bin

pnpm is only adding the executables of the direct dependencies to the root `node_modules/.bin`. The executables of subdependencies are added to the `node_modules/.bin` directories of dependent packages. This is by...

bin from optional dependencies of a devDependencies are not linked in node_modules/.bin

I see that you liked my message, so can we close this issue then?