npm ls does it, but not sure about compatibilities across the different tools
3 replies
workspace:* dependencies between packages. For reasons related to npm tags, i am not able to use pnpm -r publish (separate issue), but i use pnpm -r exec pnpm publish instead. I am seeing cases where the first publish will succeed, but subsequent publishes fail due to a dirty git repo. On investigation, the change is around swapping the workspace:* out for a concrete version
25 replies
Hi, is publishing from a detached HEAD a supported scenario? My CodeBuild CI builds recently started failing:
* EXECUTING: /codebuild/output/src336551761/src/github.com/***/config/common/temp/pnpm-local/node_modules/.bin/pnpm publish (packages/api-extractor-config)
ERROR· Command failed with exit code 128: git symbolic-ref --short HEAD
fatal: ref HEAD is not a symbolic ref
at makeError ../../../../../../../../../root/.rush/node-v12.16.1/pnpm-5.2.2/node_modules/pnpm/lib/node_modules/execa/lib/error.js:59 error = new Error(messag…
at handlePromise ../../../../../../../../../root/.rush/node-v12.16.1/pnpm-5.2.2/node_modules/pnpm/lib/node_modules/execa/index.js:114 const returnedError = ma…
at processTicksAndRejections internal/process/task_queues.js:97
at getCurrentBranch ../../../../../../../../../root/.rush/node-v12.16.1/pnpm-5.2.2/node_modules/pnpm/lib/node_modules/@pnpm/plugin-commands-publishing/lib/gitChecks.js:17 const { stdout } = await…
at handler [as publish] ../../../../../../../../../root/.rush/node-v12.16.1/pnpm-5.2.2/node_modules/pnpm/lib/node_modules/@pnpm/plugin-commands-publishing/lib/publish.js:89 if (await gitChecks_1.ge…
ERROR: The command failed with exit code 1The only change that I made since the last successful publish (around 2 months ago) was to update pnpm from 4.9.3 to 5.2.2. So I think either:
- CodeBuild's behavior recently changed to run in detached HEAD mode; or
- PNPM added a call to
git symbolic-ref HEADbetween4.9.3and5.2.2
13 replies
@/all I know there some issues with pnpm i -g on some setups. I have worked on a fix and it would be great to gather some feedback. The PR is here: pnpm/pnpm#2637
It also is published under the dev dist-tags, so you may install it via npm i -g pnpm@dev (hopefully it solves the issues with pnpm i -g pnpm as well)
33 replies
C:\Users\MyUser\AppData\Roaming\npm\pnpm in my case. Hmm.. don't know why you'd want that, a lot of other apps store configs and what not in the user folder..
I am getting a peer-dep warning with beta package installs:
WARN raw-loader@4.0.1 requires a peer of webpack@^4.0.0 || ^5.0.0 but version 5.0.0-beta.18 was installed.
WARN webpack: terser-webpack-plugin@3.0.6 requires a peer of webpack@^4.0.0 || ^5.0.0 but version 5.0.0-beta.18 was installed.I wanted to check if this behaviour is expected or incorrect before I filed an issue????
1 reply
@ that's prepended to the URL for tarball npm packages by pnpm. So I first wanted to check why this is done before working on a change to rush to accept it.
react-native: '@github.com/expo/react-native/archive/sdk-38.0.0.tar.gz_react-native@0.62.2'
lockfileVersion: 5.1"dependencies": {
"react-native": "https://github.com/expo/react-native/archive/sdk-38.0.0.tar.gz",
}dependencies:
react-native: '@github.com/expo/react-native/archive/sdk-38.0.0.tar.gz_react-native@0.62.2'@ prefix
2 replies
i am trying solve a buggy package which uses https but does not list it in its depedencieshttps://github.com/visionmedia/superagent/blob/2fcea621c69e3cc779bc59f5f3e8677c2cce8f99/src/node/index.js#L8
I used the readPackage and added the dependency:
case 'superagent':
pkg.dependencies['https'] = '^1.0.0';
break;It is added in the pnpm-lock.yaml file in the dependencies, but i still get the error:
Error: Unable to resolve module https from ../../node_modules/_pnpm/superagent/3.8.3/node_modules/superagent/lib/node/index.js
can someone point me in the correct direction how to debug this? or am i missing something ?
2 replies
pnpm buildNODE_ENV=production parcel build public/index.html --no-source-maps
pnpm install && pnpm build command again
I’m doing an experiment and perhaps you here I can get some light
{
"name": "pnpm_test",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"build": "babel --help",
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC",
"devDependencies": {
"@verdaccio/babel-preset": "^9.7.1",
"typescript": "^3.9.6"
}
}my dependency @verdaccio/babel-preset has babel as dependency but I don’t see it on my .bin folder, but I see Typescript for instance. Does anyone knows why?
pnpm command.
➜ pnpm run build
> pnpm_test@1.0.0 build /Users/jpicado/WebstormProjects/pnpm_test
> babel --help
sh: babel: command not found
ERROR Command failed.
5 replies
pnpm install -g, it installs the package to a different pnpm-global directory, which is what I expect
.pnpm-store (which was populated when I was using node v10)
pnpm install so it doesn't really matter that it uses the same .pnpm-store?
9 replies
Hey everyone! I'm running into an issue with pnpm and the vscode-eslint plugin. ESLint was supposed to run automatically, but when it tries to run I get this error:
(node:97815) UnhandledPromiseRejectionWarning: Error: Command failed: pnpm root -g
ERROR No write access to the found global executable directories
at checkExecSyncError (child_process.js:634:11)
at Object.execSync (child_process.js:670:15)
at Object.execSync (electron/js2c/asar.js:696:23)
at Object.get (/home/bruno/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.1.5/server/out/eslintServer.js:1:33524)
(...)I suspect the error is on the plugin side, and I am also opening an issue there, but I thought of asking here as well due to VSCode's recent (v 1.47) addition of official support for pnpm. I actually use VSCodium, if that makes a difference.
Any ideas for how to make the extension and pnpm work together alright?
10 replies
pnpm init next-app, blow away the node_modules directory and the package-lock.json, then re-install with pnpm, and everything would work. Now, when I do those same steps (or I even just try to install next from scratch in a clean directory), trying to run next dev causes the Error: Invalid hook call. Hooks can only be called inside of the body of a function component error. Using npm instead of pnpm works fine for the exact same code.
