[–] [S] 2 points 5 months ago

Yea I'm pretty sure I've also did this correctly since it in fact worked just fine with this electron package I've had in here for a little while now. Looking in nix-tree and searching for nodejs but the only nodejs versions I'm finding are 24.14.1 and no sign of the insecure version. Tried exporting the env and rebuilding my config but it didn't work either

  • source
  • parent
  • context
  • [–] 3 points 5 months ago (1 child)

    Several things come to mind. First, I think that you followed the instructions correctly; it doesn't look like you did anything wrong, and I'm guessing that this previously worked for Electron. Second, I would consider hunting down the insecure packages and fixing them; my main tool for this would be nix-tree. Try nix run nixpkgs#nix-tree, using the '/' key to find "nodejs" packages. Third, if you have one insecure network-facing package than you might as well consider marking the entire system as temporarily insecure and exporting NIXPKGS_ALLOW_INSECURE to the environment; this is overkill but it will tell you whether there are other extistential issues with your configuration.

  • source
  • [–] 3 points 5 months ago (1 child)

    We probably need more info. Exact commands and ideally the content of what you're evaluating (a flake I'm assuming based on what you said about inputs).

    It's hard to tell if what you've done will actually apply to the evaluation of nixpkgs in your flake, and nixpkgs may be evaluated multiple times.

  • source
  • [–] 4 points 6 months ago (1 child)

    Devenv once introduced an"feature" that uploaded your entire repo to a secret server to train their AI and didn't understand the backlash they got. There's no way they should ever be given a second chance. It is not a good recommendation.

  • source
  • [–] 2 points 6 months ago

    I do not understand your issue. If skills are simple files, why not copy them into your nixos configuration directory? Or run whatever tool exists to download them into your nixos configuration directory and commit it to git.

    What's the actual issue here?

  • source
  • [–] 0 points 6 months ago

    Still don't understand lix. It doesn't seem to provide a different ecosystem to nix and I'm not sure how it would benefit me to switch. Plugins do sound interesting however... I'd had a few ideas of what to implement for a while now.

  • source
  • [–] 1 point 6 months ago

    It's layers and layers of indirections with no clear need and technical decisions that make things unnecessarily complex.

    So your basically writing Regexes in a custom DSL in JavaScript, combined with custom hooks written in C, from which a megabytes-large native-code parser is generated.

    The complexity of the solution does not fit the niche between dead-easy TextMate grammars and plugging into an LSP.

    Don't misunderstand me, I wish there was something filling that niche, but TreeSitter 100% certainly isn't it.

  • source
  • parent
  • context
  • [–] 7 points 7 months ago

    there’s one thing that hinders unflake and native implementations alike, though: no one knows what the flakes are. documentation is lacking, and knowledge either spreads by word of mouth or is obtained by reading the source code.

    And here we have the reason I don't use flakes. If their own developers don't understand them, what kind of confidence does that give?

  • source
  • view more: ‹ prev next ›