-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support building via nix #4821
Support building via nix #4821
Conversation
Job #10195: Bundle Size — 62.34MiB (+0.02%).
Warning Bundle contains 66 duplicate packages – View duplicate packages Bundle metrics
Bundle size by type
View job #10195 report View feature/nix-docker-build-2 branch activity View project dashboard |
shell.nix
Outdated
|
||
expectedToolVersions :: [(String, [String], [String])] | ||
expectedToolVersions = | ||
[ ("pnpm", ["--version"], ["7.14.2"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add nodejs
to this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's not a bad shout
Problem:
We use nix for local development, but a series of scripts to build and deploy the actual project, leading to discrepancies between both environments that tend to cause painful issues when they arise. This has become more important now that we want to be able to use separate nix packages for building vscode vs the rest of the editor, so that we can support different node versions.
Fix:
This PR introduces the required scripts to be able to build and deploy the application using nix exclusively. It also introduces a new
vscode-build/shell.nix
for building vscode with a different version of node.Note:
As part of this I also upped the node version to v18 for the rest of the editor. I'm happy to drop that back down to v16 and introduce that change in a separate PR.