You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the VS Code extension is an NPM package, i.e. there are package[-lock].json files listing the dependencies.
As we build with Nix, we need a Nix way to convert those NPM files into Nix files.
This is currently done by node2nix.
A limitation of node2nix is that the files must be generated manually and version-controlled, meaning that:
updating the NPM dependencies always requires a manual step, which is easy to forget
NPM dependencies update automation via Dependabot opens PRs that fail CI, and require manual update to build
We originally attempted to address this problem by switching to yarn-plugin-nixify in #944 but it turns out this plugin does not seem mature enough for our use case.
There exists other solutions out there, including:
Currently the VS Code extension is an NPM package, i.e. there are
package[-lock].json
files listing the dependencies.As we build with Nix, we need a Nix way to convert those NPM files into Nix files.
This is currently done by
node2nix
.A limitation of
node2nix
is that the files must be generated manually and version-controlled, meaning that:We originally attempted to address this problem by switching to
yarn-plugin-nixify
in #944 but it turns out this plugin does not seem mature enough for our use case.There exists other solutions out there, including:
node2nix
, stores the output Nix files, thenimport
those filesThe balance is tricky to find between:
Each solution (node2nix, npmlock2nix, yarn-plugin-nixify, yarnpnp2nix, custom) seems to only check 2 out of the 3 🤷
The text was updated successfully, but these errors were encountered: