Zoltan Kochan comments

Results 827 comments of


                                            Zoltan Kochan

update meta-updater

pnpm needs to support the first LTS version of v18, which is 18.12. That setting prevents us from installing dependencies that don't support 18.12. Theoretically we could change that setting...

update meta-updater

It isn't enough to change that. You should also change the CI to run the tests on 18.12. Last time I checked, it failed.

Upgrading [email protected] of [email protected] store to [email protected] with pnpm @7.18.0 failed CI

Will be fixed by https://github.com/pnpm/pnpm/pull/8201

pnpm install "egg-mock": "^3.26.0" with pnpm-lock file get error at second times

Try to remove the store. To get the store location, run `pnpm store path`.

pnpm install "egg-mock": "^3.26.0" with pnpm-lock file get error at second times

This hopefully should be solved by https://github.com/pnpm/pnpm/pull/8201 Although I cannot reproduce the issue with `@types/superagent` at the moment.

Esbuild post-install failure with pnpm 9.3.0

We cannot fix it without steps to reproduce.

Esbuild post-install failure with pnpm 9.3.0

I couldn't reproduce the issue. Maybe there is some esbuild cache?

Can't use specifier for a snapshot dependency in the lock file

@KSXGitHub probably not intended.

I use nvm manage node, when change node from 16.x to 18.x , run pnpm xxx get pnpm not an internal or external command, nor a runnable program or batch file

You can also use pnpm to install node.js and use one less tool. https://pnpm.io/cli/env

[Regression]: ERROR Invalid string length (RangeError: Invalid string length)

We should fix it for sure but I can't reproduce the issue. This is probably the same issue as this one: https://github.com/pnpm/pnpm/issues/5056 Looks like using an object hash instead of...