| 31 Jul 2021 |
 joepie91 🏳️🌈 | and yep, exactly | 10:35:05 |
|  Tall-Lengthiness-613 joined the room. | 18:06:16 |
| 2 Aug 2021 |
|  @thereyleer:matrix.org joined the room. | 16:10:28 |
| @thereyleer:matrix.org left the room. | 16:10:57 |
| 3 Aug 2021 |
|  ult-darkcaster joined the room. | 03:21:12 |
 alkisg | On my Ubuntu 20.04, node -e require.paths is empty. If I run npm i -g module and then I try to import it, it says module not found | 07:20:57 |
| alkisg | Do I need to manually set some things like NODE_PATH, or is "global requires" supposed to be able to work out of the box, and something is wrong in my setup? | 07:21:34 |
| alkisg | Are "global requires" a bad thing? Am I supposed to use "npm link" instead? | 07:42:10 |
| alkisg | Ah, manually setting NODE_PATH makes things work. OKish... | 07:44:12 |
| alkisg | Better yet: ln -rs ~/.npm-global/lib/node_modules ~/.node_modules | 07:47:23 |
 ryzokuken | alkisg: you should really not be doing this | 07:54:49 |
| ryzokuken | if your package depends on X (by requiring it), then it should explicitly list it out as a dependency | 07:55:11 |
| ryzokuken | what you're doing right now will work, but it's not permitted for a reason | 07:55:23 |
| ryzokuken | for one, each dependency should be appropriately versioned. A different major version of the same module might break your code in a way that is impossibly hard to debug... | 07:55:58 |
| alkisg | ryzokuken: what I want is the equivalent of "suggested dependencies" of debian; i.e. I don't want npm i my-package to install these dependencies, but if the user does have them installed globally, then I can offer some additional things | 07:56:22 |
| alkisg | While optionalDependencies is the equivalent of "Recommends: " on debian; they get installed by default... | 07:56:55 |
| ryzokuken | again, why are you implying the presence of certain global dependencies? global packages are not supposed to be used this way | 07:57:31 |
| ryzokuken | or maybe you mean that package X has both your package Y and a separate package Z in its own dependency list? | 07:57:58 |
| ryzokuken | * or maybe you mean that package X has both your package Y and a separate package Z in its own dependency list? | 07:58:12 |
| alkisg | To be more specific: my sch-webapps package targets users. BUT, in very limited cases, a few developers will also use it via command line and advanced myapp developer-params options; in that case, my app does some extra stuff | 07:58:24 |
| alkisg | I don't want simple users to get the extra dependencies that a couple of devs will require; it's a bit like...internal use? | 07:58:45 |
| alkisg | What are global modules for, if not for such things? | 08:00:12 |
| alkisg | I probably misunderstood their purpose... | 08:00:23 |
| alkisg | Ah found it at https://nodejs.dev/learn/npm-global-or-local-packages | 15:13:06 |
| alkisg | Everything should be installed locally; only executables should be installed globally | 15:13:30 |
| alkisg | That indeed seems like a waste of resources, but I guess it would be difficult to properly manage versioned dependencies otherwise | 15:16:58 |
| alkisg | Hopefully this method won't be adopted by distributions, otherwise we'll end up needing 10 TB disks, as then "cp.flatpak" will need its own copies of all the system libraries, and "ls.appimage" / "cd.snap" will do the same... :D | 15:21:51 |
|  blackoutmechanix joined the room. | 23:29:33 |
| 4 Aug 2021 |
|  Benoît Vidis joined the room. | 12:27:01 |
|  ιχ joined the room. | 17:28:13 |
