3

I just finally took time to look at creating symbolic links for node modules and package and package lock json files all from a boilerplate code for my frontend projects,

I saved over 15gb of disk space,

my SSD is 40gb so that's fair

now I have all my node modules for frontend projects in a separate container and node modules for backend projects in a separate container

I still havent figured out how to trim down my package.json file before pushing because there'll be some unused libraries.

for now any direct changes I make to the package and package lock json files will be reflected in the the symlinked directory and them reflect over all projects that share it

I have to be careful here

Comments
  • 2
    How to break everything *even faster!*
  • 0
    @atheist lol, a single mistake is going to be bloody but I can manage, I have a long experience with symlinks
  • 0
    I think that pnpm is doing something like that already (without you having to do it manually).

    Other than that, 40 gigs, even if just for the OS (let alone for the OS + work), is like shooting yourself in the foot.
  • 1
    That’s an absolutely tiny ssd
  • 1
    @kamen @root harddrive failed, lost a lot and needed to get back online, I'm saving up for better one, could have gotten a used harddrive for that same price but the performance boost on a core 2 duo PC is enough sacrifice.
  • 0
    I use a system with 16 GB Storage in total, i sometimes use for works, including writing software and creating PCBs. I use about 60%.

    But i don't use bloated, slow JS software nor do i use 100's of library for my code. 40 GB is plenty when there is nothing that wastes it for nothing.
  • 0
    Had these types of issues.
    Pnpm solved this by using symlinks also
  • 1
    I'll say it again...

    NPM is shit.

    Needing symlinks is bonkers.... *shakes head*
Add Comment