| 2 Oct 2025 |
 dish [Fox/It/She] | well if they are migrated to pkgs/by-name and out of nodePackages they can stay | 04:40:25 |
| dish [Fox/It/She] | feel free to migrate them yourself if you want to | 04:40:31 |
 Emma [it/its] | ah, i dont remember if they are but oh well, worst case someone brings them back under by-name | 04:41:27 |
| dish [Fox/It/She] | prettier was migrated a while ago | 04:42:08 |
| dish [Fox/It/She] | but ts-node is still in nodePackages | 04:42:14 |
| dish [Fox/It/She] | it should be easy to migrate with the new yarn-berry lockfile tooling in nixpkgs | 04:42:27 |
| dish [Fox/It/She] | https://nixos.org/manual/nixpkgs/stable#javascript-yarn-v3-v4 | 04:43:45 |
| Emma [it/its] | Honestly i kinda liked the categorisation via nodePackages | 04:46:42 |
| Emma [it/its] | Or well, namespacing i guess | 04:47:01 |
| dish [Fox/It/She] | that would be okay | 04:58:24 |
| dish [Fox/It/She] | but not if its unmaintainable like nodePackages is | 04:58:55 |
| dish [Fox/It/She] | * but not if its unmaintainable like nodePackages is atm | 04:58:56 |
 Winter | disagree, 99.9999% of things that were shoved into nodePackages were applications, which belong at the top level | 05:01:53 |
 Sandro 🐧 | yep, it was a maintenance nightmare and regularly all kinds of things broke left, right, center and between | 14:19:46 |
 Marie | or you regenerated the thing and in the meantime someone updated it and you had to regenerate it again | 14:21:05 |
 hexa | Winter: frankly, nodePackages should have received a staggered response with milestones | 14:38:49 |
| hexa |
- trace warnings 24.05
- broken or something equally annoying 25.11
- removed in 26.05
| 14:39:30 |
| hexa | and I hope we can achieve these things with nixpkgs core | 14:39:40 |
| hexa | nodePackages still exists because we're not good at long term consistent decison making | 14:40:17 |
| hexa | but we can't even issue trace warnings, because the ci folks decided we may not | 14:41:45 |
| hexa | modules may, packages may not | 14:42:25 |
 Cobalt | How are package removals communicated then? Let's say I depend on libfoo and it gets removed (no maintainer, no dependents), wouldn't a warning be a good idea then? | 14:44:05 |
| Winter | 🙃 | 14:44:10 |
| Winter | a throw | 14:44:16 |
| Cobalt | Throw as in "package not found"? | 14:44:32 |
| hexa | throw as in "lol, its too late" | 14:47:43 |
| hexa | because we don't ship this package anymore | 14:47:57 |
| hexa | it was yanked | 14:48:01 |
| hexa | foo = throw "foo was removed from nixpkgs, because it was utter garbage" | 14:48:13 |
| hexa | * foo = throw "foo was removed from nixpkgs, because it was utter garbage";
| 14:48:16 |
