Mateusz Mazur

If you have installed it globally (with sudo) the executable should be located in `\usr\share\lotion\Lotion\Lotion` and if locally in `~\.local\share\lotion\Lotion\Lotion`. Could you try to run this executable and provide information...

For anyone still having this issue, just use: `sudo npm install -g fb-messenger-cli --unsafe-perm=true` it should fix `mkdir` problem (solution based on [this](https://github.com/puppeteer/puppeteer/issues/367#issuecomment-499315095)). Also, you may have a problem with...

I guess it might be useful for packaging older applications. It just caps minimum node.js version for running `lock-patcher.mjs`. Btw sorry for responding so late, I have missed the notification...

Yeah, I agree, although I made this change because I was packaging [Manyverse, which uses node.js version 12](https://gitlab.com/staltz/manyverse/-/blob/master/docs/getting-started.md#nodejs), so apparently this may be an issue for someone.

The best workaround for this problem is to use `--impure` flag when installing, this will result with correct installation, at least from my tests. It seems like it is a...

@lordcirth Do you mean `nixos-install --impure --flake ...` ? Actually, either way it should work as `--impure` should disable all restricted mode issues. I was installing my system about two...

I had exactly the same issue. To fix it, just restart `mysys2`. It happens probably because some environment variables need to be loaded on startup (and they are not automatically...