10 Commits

Author	SHA1	Message	Date
R. Ryantm	5b09fecd00	vsce: 3.0.0 -> 3.1.0	2024-09-05 18:40:32 +00:00
Doron Behar	24a76db073	Merge pull request #334377 from dotlambda/node-gyp ... node-gyp: init at 10.2.0	2024-08-16 15:34:47 +00:00
Aaron Jheng	4de236c910	vsce: 2.31.1 -> 3.0.0	2024-08-16 08:11:00 +00:00
Aaron Jheng	02470a2f88	vsce: move to by-name	2024-08-16 08:03:58 +00:00
Robert Schütz	000f83e17c	nodePackages.node-gyp: drop	2024-08-13 05:54:31 -07:00
pinage404	cb36a91818	vscode-runner: init at 1.6.1 (#330659)	2024-08-06 11:21:56 +02:00
R. Ryantm	6a4ae9f9d5	vscode-js-debug: 1.90.0 -> 1.91.0	2024-07-06 02:26:27 +02:00
Xandor Schiefer	92d4b33203	vscode-js-debug: darwin support	2024-06-28 00:08:53 +02:00
Xandor Schiefer	f4423979de	vscode-js-debug: fix missing jq in postPatch ... Fixes #320507. The `npmConfigHook` used by `buildNpmPackage` does not correctly propagate the `nativeBuildInputs` into its `PATH`, which is why `jq` was not available during the patch phase. Since this `npmConfigHook` is run as part of a fixed-output derivation (`fetchNpmDeps`), if it had already been realised, unless its hash had changed, a missing `jq` would not be noticed, on a rebuild of `vscode-js-debug`. The `postPatch` hook is *also* run during `buildNpmPackage`, but there the `nativeBuildInputs` were correctly added to the `PATH`, which is why a rebuild of `vscode-js-debug` with the previous `postPatch` would succeed (if its `npmDeps`'s hash hadn't changed).	2024-06-18 22:24:01 +02:00
Xandor Schiefer	2bd7c27874	vscode-js-debug: init at 1.90.0 ... Closes https://github.com/NixOS/nixpkgs/issues/281031.	2024-06-12 11:56:58 +02:00