Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command "pnpm config set store-dir" fails after upgrade to version 7.2.0 (from 7.1.9) #4877

Closed
pavelda2 opened this issue Jun 10, 2022 · 0 comments
Assignees

Comments

@pavelda2
Copy link

pnpm version: 7.2.0

Code to reproduce the issue:

curl -f https://get.pnpm.io/v6.16.js | node - add --global pnpm@7
pnpm config set store-dir .pnpm-store

Expected behavior:

Does not fail like in previous version 7.1.9 of pnpm

Actual behavior:

Fail using pnpm@7.2.0

/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:13759
          this.set("ca", output);
                         ^
ReferenceError: output is not defined
    at Conf.loadCAFile (/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:13759:26)
    at module2.exports (/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:13998:14)
    at exports2.default (/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:21797:[48](https://gitlab.dev1/kosi/kosi-ui/-/jobs/151947#L48))
    at async run (/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:1865[49](https://gitlab.dev1/kosi/kosi-ui/-/jobs/151947#L49):26)
    at async passThruToNpm (/usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:186668:22)
    at async /usr/local/pnpm-global/5/node_modules/.pnpm/pnpm@7.2.0/node_modules/pnpm/dist/pnpm.cjs:1866[50](https://gitlab.dev1/kosi/kosi-ui/-/jobs/151947#L50):7

Additional information:

  • node -v prints: v16.13.2
  • Linux (using docker image "cypress/base:16.13.2")
@zkochan zkochan self-assigned this Jun 11, 2022
zkochan added a commit that referenced this issue Jun 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants