| 30 Jul 2023 |
 gdamjan | going to sleep now ... see ya tomorrow | 03:13:06 |
| gdamjan | that's this change https://github.com/matrix-org/matrix-appservice-irc/pull/1758 | 03:13:59 |
 Lily Foster | In reply to @gdamjan:spodeli.org
but yarnLock = "${src}/yarn.lock"; would still be a problem, no?
so I need to take yarn.lock and add it to nixpkgs ? Not for fetchYarnDeps because it doesn't use the path at eval time (no import or read or anything), it's only used build time | 03:15:17 |
| Lily Foster | In reply to @gdamjan:spodeli.org
going to sleep now ... see ya tomorrow Rest well 💤 | 03:15:43 |
 dotlambda | How can I figure out which dependency causes
thread '<unnamed>' panicked at 'non-git dependencies should have assosciated integrity', src/parse/mod.rs:142:22
in https://github.com/karma-runner/karma ?
| 05:02:43 |
| dotlambda | * How can I figure out which dependency causes
thread '<unnamed>' panicked at 'non-git dependencies should have assosciated integrity', src/parse/mod.rs:142:22
when packaging https://github.com/karma-runner/karma using buildNpmPackage?
| 05:05:29 |
| dotlambda | turns out it's due to this line in package.json:
{
"devDependencies": {
"karma": "."
}
}
| 06:04:42 |
|  h7x4 joined the room. | 08:30:48 |
| Lily Foster | In reply to @robert:funklause.de
turns out it's due to this line in package.json:
{
"devDependencies": {
"karma": "."
}
}
Oh hmm, I can probably make that work if npm allows that, but does npm really allow using a package as a dev dependency of itself? | 10:50:19 |
| gdamjan | npm - everything goes | 10:50:55 |
| gdamjan | what's even the point of that | 10:51:12 |
| Lily Foster | In reply to @gdamjan:spodeli.org
what's even the point of that I think given it's a test runner that it's probably to allow them to run their own tests with itself | 10:53:22 |
