!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

210 Members
61 Servers

Load older messages


SenderMessageTime
4 May 2023
@hexa:lossy.networkhexasee the PR description23:55:50
@hexa:lossy.networkhexa

navidrome-ui> npm ERR! request to https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz failed: cache mode is 'only-if-cached' but no cached response is available.

23:56:11
@hexa:lossy.networkhexabasically this23:56:13
@lily:lily.flowersLily FosterOh that's during dep build, not during fetching. And yeah that is what the just-merged PR should fix23:56:33
@hexa:lossy.networkhexait did.23:56:52
@hexa:lossy.networkhexahave been waiting for this change since the end of january 😄23:57:03
@hexa:lossy.networkhexaokay, nvm23:57:12
@hexa:lossy.networkhexadeleted my postInstall thing and tada.wav23:57:24
@hexa:lossy.networkhexaso let me retry with overwriting the complete installPhase23:58:06
@lily:lily.flowersLily FosterI just checked the package-lock.json and no git deps so you shouldn't need https://github.com/NixOS/nixpkgs/pull/206477 at least. I plan to get that one in too in the next week. I pushed what is hopefully the final diff a bit ago, but I need to do testing to make sure it is actually working as intended23:58:53
5 May 2023
@hexa:lossy.networkhexaI also had one that had a git dependency00:06:53
@hexa:lossy.networkhexabut it is so long ago, I don't even remember which one it was00:07:02
@hexa:lossy.networkhexanavidrome ui looks good.00:07:28
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
but it is so long ago, I don't even remember which one it was
Hopefully those will work okay enough soon.... Npm just keeps finding new and surprising ways to make those utterly busted though
00:08:41
@hexa:lossy.networkhexathanks for working on these issues nevertheless00:09:03
@lily:lily.flowersLily Foster(after 206477 and some code to deal with npm workspaces, I will consider npm stuff "reasonably usable" -- right now it's pretty hit-or-miss though and obviously we would still have yarn, pnpm, etc to deal with once npm is fine)00:10:16
@lily:lily.flowersLily Foster * (after #206477 and some code to deal with npm workspaces, I will consider npm stuff "reasonably usable" -- right now it's pretty hit-or-miss though and obviously we would still have yarn, pnpm, etc to deal with once npm is fine)00:10:21
@hexa:lossy.networkhexaindeed, looking forward to yarn, to build home-assistants ui from source00:10:41
@hexa:lossy.networkhexaand then we can hopefully tackle most of nodePackages00:10:55
@hexa:lossy.networkhexaideally we would just mark all of nodePackages broken at some point00:11:14
@lily:lily.flowersLily Foster Yeah, I have two open fixes to the fetchYarnDeps fetcher and then we can make those work with buildYarnPackage and then no more yarn2nix-moretea or whatever it's called now 00:11:26
@hexa:lossy.networkhexayeah, I've used yarn2nix-moretea and the defaults are borderline IFD00:11:55
@hexa:lossy.networkhexa * yeah, I've used yarn2nix-moretea and its defaults are borderline IFD00:13:12
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
navidrome ui looks good.
When/how did you get that npmDepsHash? I'm getting a different one locally
00:16:13
@hexa:lossy.networkhexaprobably still from before your changes got merged00:16:53
@lily:lily.flowersLily FosterAh that would be why00:17:00
@hexa:lossy.networkhexathanks for checking00:17:11
@lily:lily.flowersLily Foster I get sha256-qxwTiXLmZnTnmTSBmWPjeFCP7qzvTFN0xXp5lFkWFog= locally so maybe try that 00:17:13
@lily:lily.flowersLily Foster(can't wait to have the time/bandwidth to finish my FOD reproducibility checker for nixpkgs... they're like landmines when you find a broken FOD)00:18:00
@hexa:lossy.networkhexa
navidrome-ui-0.49.3-npm-deps> node_modules/@typescript-eslint/type-utils
navidrome-ui-0.49.3-npm-deps> node_modules/@typescript-eslint/types
navidrome-ui-0.49.3-npm-deps> Error: https://registry.npmjs.org/postcss-minify-font-values/-/postcss-minify-font-values-5.1.0.tgz: sta
00:18:03

Show newer messages


Back to Room ListRoom Version: 6