!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
61 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
9 Nov 2023
@lily:lily.flowersLily Foster
In reply to @szucsitg:matrix.org

I am trying to build a frontend with mkYarnPackage but it fails on download for this lockfile

# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1


"duo_web_sdk@https://github.com/duosecurity/duo_web_sdk#v2.9":
  version "2.7.0"
  resolved "https://github.com/duosecurity/duo_web_sdk#378e855ce4a1de1d1b2f7fd60465e564b3e9fbda"

The error is:

error: hash mismatch in fixed-output derivation '/nix/store/yxmkgwcrvzfmhhxjqkrcnd49fr8fv1bi-duosecurity_duo_web_sdk.drv':
         specified: sha1-N46FXOSh3h0bL3/WBGXlZLPp+9o=
            got:    sha1-DbsHW3BaLQrtZoh0x5znwdK9xAc=

I'm not sure why the hash doesn't align

Okay so the answer is yarn2nix's bespoke, custom lockfile parsing is bad
16:44:56
@lily:lily.flowersLily Fosterand it is assuming the git url is not a git url but a tarball url and that the rev is not a rev but the actual hash16:45:11
@lily:lily.flowersLily Fosterwhich is of course wrong16:45:14
@lily:lily.flowersLily Fosterand the reason it doesn't just get an eval error16:45:24
@lily:lily.flowersLily Foster(which it should)16:45:27
@szucsitg:matrix.orgszucsitgThanks for debugging. I was looking through the yarn2nix code, and I think I found a work around. Use the tag's source tar.gz from github16:46:13
@lily:lily.flowersLily Fostermaybe just change this line: https://gist.github.com/szucsitg/70fe7ca82c51d30208595cd04b8bd7c5#file-package-json-L516:46:15
@lily:lily.flowersLily Foster to git+https://... 16:46:19
@lily:lily.flowersLily Foster
In reply to @szucsitg:matrix.org
Thanks for debugging. I was looking through the yarn2nix code, and I think I found a work around. Use the tag's source tar.gz from github
Those tarballs aren't exactly guaranteed to never change (and indeed they have in the past) so that might explode some dahy
16:46:54
@lily:lily.flowersLily Foster
In reply to @szucsitg:matrix.org
Thanks for debugging. I was looking through the yarn2nix code, and I think I found a work around. Use the tag's source tar.gz from github
* Those tarballs aren't exactly guaranteed to never change (and indeed they have in the past) so that might explode some day
16:46:55
@lily:lily.flowersLily FosterLetting yarn2nix download it as a git repo is probably better16:47:05
@lily:lily.flowersLily Foster And it looks like they should support git+https://github.com/duosecurity/duo_web_sdk.git#v2.9 correctly 16:47:29
@szucsitg:matrix.orgszucsitgLet me try this16:48:02
@szucsitg:matrix.orgszucsitgIt's working 🥳 now i can continue fixing missing package references in our own packages 😅16:55:39
@szucsitg:matrix.orgszucsitgThanks again for your help 🙂16:55:48
@lily:lily.flowersLily Fosteroh good! glad it was that easy to fix16:58:37
@szucsitg:matrix.orgszucsitg The next one will be more difficult because our own packages are not in the lock file 17:02:30
10 Nov 2023
@janne.hess:helsinki-systems.deJanne Heß Soooo Lily Foster I found my issue. The lock file was too old. Is this issue known in nix-prefetch-npm? 09:11:03
@janne.hess:helsinki-systems.deJanne HeßIssue is that the downloads just deadlock at some point09:11:21
@janne.hess:helsinki-systems.deJanne HeßFull reproducer with the original files: https://github.com/dasJ/broken-npm-test09:20:23
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de
Full reproducer with the original files: https://github.com/dasJ/broken-npm-test
Spooky, i'll try your reproducer later and see what's up
12:21:05
@szucsitg:matrix.orgszucsitgI managed to figure out how to build the project mkYarnPackage. I added all packagges as workspaceDependencies, and it displays correctly in the offline cache derivation under node-modules (symlinked from deps). However when I want to build the React frontend a few folders down, it cannot find our own packages, while the node_modules folder correctly symlinked in root to offlineCache.16:14:45
@szucsitg:matrix.orgszucsitg* I managed to figure out how to build the project mkYarnPackage. I added all packagges as workspaceDependencies, and it displays correctly in the offline cache derivation under node-modules (symlinked from deps). However when I want to build the React frontend a few folders down, it cannot find our own packages, while the node_modules folder correctly symlinked in root to offlineCache. Anybody seen such behavior?16:15:00
@lily:lily.flowersLily Foster
In reply to @szucsitg:matrix.org
I managed to figure out how to build the project mkYarnPackage. I added all packagges as workspaceDependencies, and it displays correctly in the offline cache derivation under node-modules (symlinked from deps). However when I want to build the React frontend a few folders down, it cannot find our own packages, while the node_modules folder correctly symlinked in root to offlineCache.
i really think trying to symlink node_modules like that is gonna cause more problems than it will solve
16:15:30
@lily:lily.flowersLily Fosterwhat's in that "few folders down" you're referring to?16:15:44
@lily:lily.flowersLily Foster(e.g. a new yarn package entirely or workspace package or what?)16:15:58

Show newer messages


Back to Room ListRoom Version: 6