No internet connection
  1. Home
  2. Support

Stuck at the starting talkyard

By 刘志力 @liuzhili
    2024-10-16 03:43:05.665Z

    When I followed the instructions in the starting-talkyard.md document to run talkyard. I got stuck at the nix-shell step.

    Here is the output when I start the nix-shell:

    error: nodejs_14 has been removed as it is EOL.
    (use '--show-trace' to show detailed location information)
    

    Who can help me? Thank you.

    Solved in post #4, click to view

    Linked from:

    1. support-chat
    • 5 replies
    1. Hi 刘志力, I'm using nixos-22.11 with Talkyard — I think Nodejs 14 is still available in NixOS 22.11 (but apparently not in the more recent 24.x Nix packages).

      If you want, you could try with nixos-22.11 instead?

      It'd be nice to upgrade to a more recent NixOS version soon. (B.t.w., Talkyard uses Nodejs for transpiling typescript and bundling scripts and running end-to-end tests, but not in production.)

      1. L刘志力 @liuzhili
          2024-10-18 03:41:54.580Z

          Thank you for your reply.
          I downgraded my Nix from version 2.9.2 to 2.5.1 on my Windows 10 WSL Ubuntu subsystem. But when I run nix-shell the console output the same content.

          error: nodejs_14 has been removed as it is EOL.
          (use '--show-trace' to show detailed location information)
          

          I'm completely out of options due to my limited knowledge of niv.

          1. downgraded my Nix version

            Now I'm not an expert on Nix, but I suspect that this won't change what packages with 3rd party software (like Nodejs) one uses — only the version of the Nix binaries.

            my limited knowledge of niv

            Me too — I look into the Nix config so infrequently, so I tend to forget everything in between, and need to relearn.

        • L
          In reply toliuzhili:
          刘志力 @liuzhili
            2024-10-18 04:45:37.027Z

            Now it's resolved.I was stuck there due to my limited knowledge of niv.
            I resolved the issue through the following steps.

            1, To temporarily allow all insecure packages (use an environment variable for a single invocation of the nix tools)

            $ export NIXPKGS_ALLOW_INSECURE=1
            

            2, Running nix-shell by using a fixed version of Nixpkgs configuration.

            nix-shell  -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/a71323f68d4377d12c04a5410e214495ec598d4c.tar.gz
            

            "a71323f68d4377d12c04a5410e214495ec598d4c" is a speical nixpkgs reference, you can find the right nixpkgs reference at https://www.nixhub.io/.

            ReplySolution
            1. Ok nice that there was a solution :- )   One idea: You could add a calendar event, 1 or 2 years from now, about removing the NIXPKGS_ALLOW_INSECURE setting, so you won't forget (because by then, likely Talkyard uses a newer version of the Nix packages, and the problem is gone).

            2. Progress
            3. L@liuzhili accepted an answer 2024-10-19 02:48:09.373Z.