Offline
My 2 cents worth.
@Jalibu I agree with your view.
It is highly recommended you commit the generated package lock to source control: this will allow anyone else on your team, your deployments, your CI/continuous integration, and anyone else who runs npm install in your package source to get the exact same dependency tree that you were developing on.
@KristjanESPERANTO Personally I always add it to .gitignore along with node_modules folder.
@rkorell Just read that X11 is still there in Trixie. So no stress yet, but yes, it is old and may be on it’s way out one of these good ol days.
@plainbroke There you go. Use the upgrade script by @sdetweil with the apply option and it should sort out your modules’ missing dependencies. If you still have issues then post the logs so we can see what else is wrong.
@cowboysdude Awesome. I swear I could not find it anywhere ;-)
@KristjanESPERANTO My 20pence/cents worth, I vote to make this the official page. We need to move with the times and the old page is outdated.
@BKeyport X11 does not work for me, hence I use Wayfire. As Labwc is supposed to be the newer lighter compositor, I would like to get that to work for me.
@ankonaskiff17 SO I believe a few things have changed since. Some deprecated modules they got rid off i.e. request and some others. Modules that use them would be a problem. My suggestion would be to use Sam’s upgrade script which would check each module directory and fixup the missing dependencies for you.
@BKeyport As an IT person I would say we need to move with the times. Being stuck in the old is never good. Have you tagged your modules as per the stats gathered on it?
@ember1205 Easiest way for me was installing the Adguard plugin on Chrome