| 7 Sep 2025 |
|  Ab Kein joined the room. | 04:51:50 |
| 9 Sep 2025 |
|  amaan set a profile picture. | 07:59:21 |
| amaan changed their profile picture. | 07:59:36 |
| amaan changed their profile picture. | 07:59:55 |
| 10 Sep 2025 |
|  SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (@nixcon & back on matrix) to SomeoneSerge (back on matrix). | 00:38:07 |
| 12 Sep 2025 |
|  @aidalgol:tchncs.de set a profile picture. | 09:21:40 |
| 18 Sep 2025 |
|  mmkaram joined the room. | 08:33:21 |
| mmkaram | hello! I was trying to install the @prisma/language-server package from nixpkgs but it was marked as broken in March. It has since been fixed on npm, so I was thinking of trying to make a pr to add it back. The PR that removed it is here: https://github.com/NixOS/nixpkgs/commit/8af4a78d0d0486de96e0207eba72ff43382eb2dd
My question is all they changed was pkgs/development/node-packages/node-packages.json and pkgs/development/node-packages/main-programs.nix. There was no actual package.nix that was changed. To revert this change, would I just have to add the lines that were removed back? | 08:33:30 |
| mmkaram | I initially posted this in #dev:nixos.org but I was told that people here could help me with the details because nodePackages is supposed to be phased out or something | 08:34:19 |
 Marie | in theory yes, in practice no.
Ideally you would package it from source in a new package in pkgs/by-name/pr/prisma-language-server | 08:37:45 |
| mmkaram | I’m sure it can’t be that difficult I’ll try my hand at it today | 08:41:31 |
| mmkaram | Does anyone remember the name of the formatter for nix files? | 08:42:00 |
| Marie | nixfmt | 08:45:32 |
| mmkaram | right, probably could've guessed that... thank you | 08:45:53 |
| mmkaram | are there any examples of programs like mine that have been packaged in /pkgs/by-name | 08:58:48 |
| Marie | anything which uses buildNpmPackage really | 09:02:07 |
| Marie | it's also documented in the nixpkgs manual | 09:02:12 |
| mmkaram | awesome! | 09:04:31 |
| mmkaram | for the name should I keep it as @prisma/language-server because the contrib manual says to keep the name the same as upstream | 09:04:49 |
| mmkaram | but also I know things with @ symbols aren't indexed on search.nixos.org | 09:05:03 |
| Marie | uh that sounds wrong, where does it say that? | 09:05:34 |
| Marie | prisma-language-server would be my suggestion | 09:05:51 |
| mmkaram | https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#:~:text=It%20should%20be%20identical%20to%20the%20upstream%20package%20name. | 09:06:20 |
| Marie | oh yeah thats not a hard requirement | 09:08:39 |
| mmkaram | sweet | 09:08:58 |
| mmkaram | would anyone here happen to have encountered this error before:
> npm error code ENOTCACHED
> npm error request to https://registry.npmjs.org/universal-user-agent failed: cache mode is 'only-if-cached' but no cached response is available.
> npm error A complete log of this run can be found in: /build/cache/_logs/2025-09-18T09_38_35_036Z-debug-0.log
| 09:39:19 |
| mmkaram | here is my package.nix as it is:
{
lib,
buildNpmPackage,
fetchFromGitHub,
}:
buildNpmPackage (finalAttrs: {
pname = "prisma-language-server";
version = "6.16.2";
src = fetchFromGitHub {
owner = "prisma";
repo = "language-tools";
tag = "v${finalAttrs.version}";
hash = "sha256-x4lYhS8PJ5paFJDAXGtKv0kY01C/YWaJU640WlJT8Eo=";
};
npmDepsHash = "sha256-QMxu2AWGRQ2semp6BmOQbM7Pw/pS0mgx0P0hr60SjPs=";
# The prepack script runs the build script, which we'd rather do in the build phase.
npmPackFlags = [ "--ignore-scripts" ];
makeCacheWritable = true;
NODE_OPTIONS = "--openssl-legacy-provider";
meta = {
description = "";
homepage = "https://github.com/prisma/language-tools#readme";
license = lib.licenses.asl20;
maintainers = with lib.maintainers; [ mmkaram ];
};
})
| 09:39:35 |
| Marie | yes their lockfile is broken | 09:41:30 |
| Marie | thats an issue which has been known for years now and npm doesn't consider it a bug | 09:41:51 |
| mmkaram | exciting. | 09:42:07 |
