| 30 Jan 2024 |
Marie | no, but the project is a workspace and the dependencies with issues seem to be used in different versions across workspace packages | 10:11:09 |
Wanja Hentze | oh, I've seen that with workspaces too, but sadly don't remember the fix :/ | 10:18:57 |
Marie | i get a different lockfile with a different runtime error when generating the lockfile on a non NixOS machine, with the same nodejs package from nixpkgs 😵💫 | 10:49:47 |
Wanja Hentze | hey, npm can barely behave reproducibly when given an existing lockfile, and you're expecting lockfile generation to be reproducible? :D | 10:59:57 |
Marie | fair | 11:10:43 |
Marie | but getting very different lockfiles from the exact same version doesn't look good | 11:17:38 |
Lily Foster | In reply to @marie:marie.cologne I can't get npm to write a non broken lockfile for me, any ideas? I tried with npm 9.8.1, 10.2.4 and 1.4.0 on different systems and all don't add integrity and resolved fields for a few dependencies I tried running npm-lockfile-fix but this also seems to break the lockfile can you share package.json and the lockfile? | 11:56:55 |
Marie | In reply to @lily:lily.flowers can you share package.json and the lockfile? upstream lockfile: https://github.com/appium/appium/blob/master/package-lock.json lockfile i got on non nixos system: https://github.com/appium/appium/blob/6365189b729548fe0e1591000634291c7e7a126c/package-lock.json lockfile from nixos system: https://github.com/appium/appium/blob/591bc0f96eeebb72252d7eb996ef0068993c23e1/package-lock.json | 12:41:17 |
Lily Foster | (maybe we should just dump npm and only use pnpm. pretty sure it's lockfiles are significantly less busted out in the wild) | 12:42:35 |
Lily Foster | * (maybe we should just dump npm and only use pnpm. pretty sure its lockfiles are significantly less busted out in the wild) | 12:42:45 |
Marie | i got another clue from a colleague, i forgot to delete the subpackage node_modules folders. that might explain the package lock differences | 12:47:34 |
Marie | but it still throws an error when trying to run it, not sure if that is buildNpmPackage's fault | 12:48:36 |
Marie | i'll try to debug that another time | 12:49:32 |
Lily Foster | In reply to @marie:marie.cologne but it still throws an error when trying to run it, not sure if that is buildNpmPackage's fault share log? | 13:04:04 |
Marie | oh sorry, forgot to send
/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/node_modules/ajv-formats/src/index.ts:55
ajv.opts.code.formats ??= _`require("ajv-formats/dist/formats").${exportName}`
^
TypeError: Cannot read properties of undefined (reading 'code')
at addFormats (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/node_modules/ajv-formats/src/index.ts:55:12)
at formatsPlugin (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/node_modules/ajv-formats/src/index.ts:42:3)
at Function._instantiateAjv (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/packages/appium/lib/schema/schema.js:256:27)
at new AppiumSchema (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/packages/appium/lib/schema/schema.js:102:30)
at Function.create (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/packages/appium/lib/schema/schema.js:114:24)
at Object.<anonymous> (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/packages/appium/lib/schema/schema.js:663:35)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32)
at Function.Module._load (node:internal/modules/cjs/loader:1023:12)
at Module.require (node:internal/modules/cjs/loader:1235:19)
at require (node:internal/modules/helpers:176:18)
at Object.<anonymous> (/nix/store/7v1595gwyl2lrsb9dx1n8f0vig81l454-appium-2.4.1/lib/node_modules/appium-monorepo/packages/appium/lib/config.js:9:1)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32)
| 13:08:34 |
| 31 Jan 2024 |
| @federicodschonborn:matrix.org changed their profile picture. | 03:35:49 |
| @federicodschonborn:matrix.org changed their profile picture. | 06:21:18 |
| 1 Feb 2024 |
hexa | https://github.com/NixOS/nixpkgs/issues/277697 | 15:02:30 |
hexa | rip | 15:02:30 |
hexa | apparently we are already on 4.2.4, so no idea 😄 | 15:06:33 |
Lily Foster | In reply to @hexa:lossy.network apparently we are already on 4.2.4, so no idea 😄 4.2 branch is still v1 lockfile, even 4.2.5 | 17:13:46 |
hexa | yeah, no idea | 17:14:06 |
hexa | found this on the fediverse | 17:14:15 |
Lily Foster | it will need to be fixed before 4.3 or something, presumably | 17:14:44 |
| 2 Feb 2024 |
teto | Is it expected for npm link to fail ? from a nix develop with buildNpmPackage
➜ npm link package.json
npm ERR! code ENOENT
npm ERR! syscall mkdir
npm ERR! path /nix/store/d6lkbndr98lcn8spbqxfq52f2ldvqhks-nodejs-20.11.0/lib/node_modules/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, mkdir '/nix/store/d6lkbndr98lcn8spbqxfq52f2ldvqhks-nodejs-20.11.0/lib/node_modules/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
| 12:59:02 |
Lily Foster | In reply to @keiichi:matrix.org
Is it expected for npm link to fail ? from a nix develop with buildNpmPackage
➜ npm link package.json
npm ERR! code ENOENT
npm ERR! syscall mkdir
npm ERR! path /nix/store/d6lkbndr98lcn8spbqxfq52f2ldvqhks-nodejs-20.11.0/lib/node_modules/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, mkdir '/nix/store/d6lkbndr98lcn8spbqxfq52f2ldvqhks-nodejs-20.11.0/lib/node_modules/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
i just looked it up to double check, but npm link operates on the global prefix apparently (i.e. the dir node is "installed" to) so yeah without changing the prefix via npm config, it's not gonna do anything useful from nix | 13:05:51 |
Lily Foster | (regardless of being in a dev shell, i imagine) | 13:06:07 |
teto | it seemed like it but I preferred to be sure ty | 13:06:59 |
| 5 Feb 2024 |
| @ThorHop:matrix.org removed their profile picture. | 22:45:11 |
| @ThorHop:matrix.org removed their display name IdeallyYes. | 22:46:21 |