-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[Feat]: More sync between nixpkgs version and repo version #6633
Comments
Yeah I have been trying to get nixpkgs updated but I just keep running into issues. I got an error similar to the above, it seems to be the line in the install phase that installs production dependencies. I see that we use
And I have not looked into this yet. But it feels like maybe I just made a typo somewhere. |
@code-asher I've advanced a little bit in this, however yarn/npm and js ecosystems are not my topic. I managed to compile the latest code-server version modifying it slightly with this commit: I had problems with argon2 module missing when trying to execute the app, after that, I manage to go further, but still encounter problems. I think that this is something that probably someone experienced can easily handle.
|
Ah yeah probably because of |
I bet the post-install scripts are responsible for building the native modules like |
What is your suggestion?
It would be nice if the NixPkgs version is always up-to-date with the latest release.
Why do you want this feature?
In can only install code-server through nix due to some requirements, and I would like to always have the up-to-date version, specially important due to copilot/copilot-chat
Are there any workarounds to get this functionality today?
I can modify the nixpkgs and build it locally.
Are you interested in submitting a PR for this?
I may be interested to maintain nixpkgs version, but when I tried to modify the nixpkgs repository, I failed to compile due to some yarn errors, that I don't know if they are my fault or that this pkg needs to be compiled with some extra nix configs.
The text was updated successfully, but these errors were encountered: