!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
59 Servers

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


SenderMessageTime
17 Jan 2024
@lily:lily.flowersLily Fostererr wait, no maybe i haven't found the bug. that didn't work. give me a few23:20:45
@h7x4:nani.wtfh7x4No worries 😄 Ping me if you'd like the package file with the current failing setup.23:23:45
@lily:lily.flowersLily Foster
In reply to @h7x4:nani.wtf
No worries 😄 Ping me if you'd like the package file with the current failing setup.
sure, i made my own super quickly but that would probably help too
23:25:48
@lily:lily.flowersLily Fosteri'm starting to wonder if this is just an npm bug? at least in my reproducer, it has nothing to do with lockfile fixup afaict23:30:04
@lily:lily.flowersLily Fosternpm says "tarball data seems to be corrupted" even though hash matches and the tarball seems valid 🤔23:30:38
@h7x4:nani.wtfh7x4

I've bundled a patch, likely introducing IFD, but good enough for testing.

{ lib
, buildNpmPackage
, fetchNpmDeps
, fetchFromGitea
, git
, cacert

, writeText
}:
# Smaller version of the problem
# fetchNpmDeps {
#   name = "out-of-your-element-deps";
#   src = fetchFromGitea {
#     domain = "gitdab.com";
#     owner = "cadence";
#     repo = "out-of-your-element";
#     rev = "v1.3";
#     hash = "sha256-dLDm3xOMoprkGU7D9IFX1hjMfCR3YjVgXb3c5IEuUTQ";
#   };

#   patches = [ ./add-discord-markdown-dep-integrity.patch ];

  # npmDepsHash = "sha256-k2MeejRWteIzY1Q+iNLCLDLnE1z9+cBaAGYAIlQHa/4=";
# };
buildNpmPackage rec {
  pname = "out-of-your-element";
  version = "1.3";
  src = fetchFromGitea {
    domain = "gitdab.com";
    owner = "cadence";
    repo = "out-of-your-element";
    rev = "v${version}";
    hash = "sha256-dLDm3xOMoprkGU7D9IFX1hjMfCR3YjVgXb3c5IEuUTQ";
  };

  patches = [ (writeText "add-discord-markdown-dep-integrity.patch" ''
    diff --git i/package-lock.json w/package-lock.json
    index 3847ee1..79a3ac0 100644
    --- i/package-lock.json
    +++ w/package-lock.json
    @@ -1060,6 +1060,7 @@
         "node_modules/discord-markdown": {
           "version": "2.4.1",
           "resolved": "git+https://git.sr.ht/~cadence/nodejs-discord-markdown#abc56d544072a1dc5624adfea455b0e902adf7b3",
    +      "integrity": "sha512-mPjPXXNgL3prKagvj/guOzAEMcJdcr6S95u7MRlYZvsgeUiacQDQatYrJgYAf53vJw+U0JvEPUwRHZY02oX1og==",
           "license": "MIT",
           "dependencies": {
             "simple-markdown": "^0.7.2"
  '') ];

  dontNpmBuild = true;
  npmDepsHash = "sha256-fPTFyX2GYSdMeIzVKXBacZxhTTj8fvlMFEGOxN0/cm8=";

  meta = with lib; {
    homepage = "https://gitdab.com/cadence/out-of-your-element";
    description = "Modern Matrix-to-Discord appservice bridge";
    changelog = "https://gitdab.com/cadence/out-of-your-element/releases/tag/${src.rev}";
    license = licenses.agpl3Plus;
    mainProgram = "start.js";
  };
}
23:34:11
@lily:lily.flowersLily Fostergods i wish npm's debug logging wasn't so slim and convenient not say where or why the error actually happened...23:57:46
@lily:lily.flowersLily Foster * gods i wish npm's debug logging wasn't so slim and not say where or why the error actually happened...23:57:55
18 Jan 2024
@syntheit:matrix.org@syntheit:matrix.org left the room.04:14:31
19 Jan 2024
@ThorHop:matrix.org@ThorHop:matrix.org changed their display name from hopland (meticulous montesquieu) to hopland (manners or stfu).05:12:19
@ThorHop:matrix.org@ThorHop:matrix.org changed their display name from hopland (manners or stfu) to hopland.05:14:42
22 Jan 2024
@szucsitg:matrix.orgszucsitgWhat is the right way to not copy node_modules into lib folder with buildNpmPackage? As it's a static frontend code it doesn't need that folder at all09:37:28
@szucsitg:matrix.orgszucsitg Ah, I guess I should have just added dontInstall = true 😅 09:51:24
@marie:marie.cologneMarieyou could also set installPhase for copying the build output to $out10:36:20
@ThorHop:matrix.org@ThorHop:matrix.org changed their display name from hopland to IdeallyYes.15:06:40
29 Jan 2024
@hexa:lossy.networkhexaRedacted or Malformed Event22:31:06
@hexa:lossy.networkhexafetchNpmDeps chokes on fetching cryptpad things 😄 22:31:33
@hexa:lossy.networkhexa this looks an issue avocadoom solved by exporting HOME, but since it happens in the fetcher for me....? 22:32:00
@hexa:lossy.networkhexa * this looks an issue avocadoom solved by exporting HOME 22:37:19
@hexa:lossy.networkhexa * fetchNpmDeps chokes on cryptpad things 😄 22:37:43
@hexa:lossy.networkhexa * buildNpmPackage chokes on cryptpad things 😄 22:37:49
@hexa:lossy.networkhexabut doing that doesn't help 🙂22:44:13

Show newer messages


Back to Room ListRoom Version: 6