Nix NodeJS | 203 Members | |
| 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Nov 2023 | ||
| idk how yarn or yarn2nix does peer dep handling | 13:50:00 | |
| yarn 1.x treats peer dependencies as optional dependencies; it does not automatically install them, and just produce a warning if they are missing. this is what used to be the behaviour of npm as well. I don't know if newer Yarn versions have changed this | 13:51:37 | |
| * yarn 1.x treats peer dependencies as optional dependencies; it does not automatically install them, and just produces a warning if they are missing. this is what used to be the behaviour of npm as well. I don't know if newer Yarn versions have changed this | 13:51:43 | |
In reply to @joepie91:pixie.townbut it otherwise does the circular resolution okay? i figure it's probably a yarn2nix bug anyway (there seems to be no shortage of those, unfortunately...) | 13:52:32 | |
| I think circular dependencies are undefined behaviour in JS modules? | 13:54:36 | |
| not sure how Yarn handles those in general actually | 13:54:45 | |
| typical peer dependency use would involve one 'primary' package and a bunch of eg. plugin packages that peer-depend on that primary package; I've never really seen peer dependencies used outside of plugin architectures like that | 13:55:23 | |
| so that wouldn't be circular, exactly | 13:55:43 | |
| yeah i suppose they're not designed to be circular, but i thought they were designed to be used in scenarios that otherwise might be circular, like plugin deps | 13:57:30 | |
| idk i need coffee anyway and brain is not working well yet | 13:57:45 | |
| (i'd definitely trust your judgement way more than my own on this anyway) | 13:58:46 | |
| I checked the code they really cross-referenced the project while not even declaring the module in package.json 🙄🤦♂️ | 13:59:51 | |
| perhaps there are circular plugin architecures, but usually it's more something like
and so both the "core" package and the plugin packages are loaded from the application code, the plugins don't load the core and the core doesn't load the plugins, the peer dependency constraint just serves to give people a warning if they have an incompatible core and plugins in the same project | 14:02:22 | |
| * perhaps there are circular plugin architecures, but usually it's more something like
and so both the "core" package and the plugin packages are loaded from the application code, the plugins don't load the core and the core doesn't load the plugins, the peer dependency constraint just serves to give people a warning if they have an incompatible core and plugins in the same project | 14:02:28 | |
| I wonder if it's possible to just install a list of dependencies https://github.com/svanderburg/node2nix#adding-unspecified-dependencies , like having a package.json
npm update doesn't work so I think not. My original issue is that right now I need to use | 14:09:55 | |
| 15 Nov 2023 | ||
| 12:41:52 | ||
| 16:10:49 | ||
| 16:10:49 | ||
| 17:38:27 | ||
| It's funny how no one seems to be using typescript https://www.reddit.com/r/Nix/comments/x7tdxd/building_typescript_node_apps_with_nix/ https://www.reddit.com/r/NixOS/comments/16xlbk2/looking_for_help_to_use_nixos_in_a_typescript/ | 17:41:43 | |
| 17:48:57 | ||
| 18:12:40 | ||
| 18:12:40 | ||
In reply to @keiichi:matrix.orgWe do use typescript, it's just compiled to JS in the build step. Otherwise, ts-node from nuxpkgs works too | 19:11:41 | |
| 16 Nov 2023 | ||
| 05:13:13 | ||
| think I kinda managed to package my typescript program with buildNpmPackage but on run I get
usually I can manage this kind of issues with a bit of NODE_PATH shenaningan but the files dont seem to even exist in | 09:51:55 | |