Comments (20)
Fixed in #1719
from nixvim.
The issue is we are using an old package name for the bash language server.
This should only affect you if you are overriding nixvim's nixpkgs lock (i.e.
nixvim.inputs.nixpkgs.follows
).Until we fix this in See #1696, you should either remove/comment out your "nixvim follows" line, or rollback your flake.lock to an older nixpkgs revision.
EDIT: upstream PR is NixOS/nixpkgs#319882
I had same issue with "error: Alias @astrojs/language-server is still in node-packages.nix" just removed "nixpkgs.follows" solved the issue.
from nixvim.
The issue is we are using an old package name for the bash language server.
This should only affect you if you are overriding nixvim's nixpkgs lock (i.e. nixvim.inputs.nixpkgs.follows
).
Until we fix this in See #1696, you should either remove/comment out your "nixvim follows" line, or rollback your flake.lock to an older nixpkgs revision.
EDIT: upstream PR is NixOS/nixpkgs#319882
from nixvim.
Just had this and fixed this issue by removing nixvim.inputs.nixpkgs.follows
but you have to also run nix flake update
, or similar command to just update that one flake, as well. Which was not immediately obvious to me.
from nixvim.
Just had this and fixed this issue by removing
nixvim.inputs.nixpkgs.follows
but you have to also runnix flake update
, or similar command to just update that one flake, as well. Which was not immediately obvious to me.
If you want to apply input changes to flake.lock
without also updating, you can use nix flake lock
.
Incidentally, if you want to change what an input points to without modifying your flake.nix
(e.g. to temporarily test a PR or revert to an old rev) you can use nix flake lock --override-input <input-name> <input-url>
.
from nixvim.
I was still getting the error after removing the "follows" line. I ended up pinning my nixpkgs input to the same rev as the nixpkgs input for nixvim and that worked fine as expected.
from nixvim.
I was still getting the error after removing the "follows" line
Did you run nix flake lock
after removing the follows
?
from nixvim.
After removing the follows
and running both nix flake update
and nix flake lock
multiple times, I still get the same build error. Is there any information I can provide to try to find a solution to this, or would it be easiest to wait for #1696?
from nixvim.
If
follows
is not having an effect, try overriding your main nixpkgs input (the one that becomespkgs
in your modules) to point to a nixpkgs without this issue. We're currently locked to57d6973abba7ea108bac64ae7629e7431e0199b6
.
Using this commit, I no longer get this error, both with and without follows. Thank you!
I'm curious which installation method you use for nixvim (nixos, hm, darwin, standalone), it may be this determines whether nixvim evaluate using its own nixpkgs input or the
pkgs
of a wider module system.
I'm using a standalone nixvim
flake on my system running NixOS x86_64-linux
and just add the output of the standalone flake to my system packages.
from nixvim.
The update has now made it into nixpkgs. Now #1702 is stopping me from building, but this is a separate issue.
It's not yet in nixos-unstable
. It's in all the other channels though: https://nixpk.gs/pr-tracker.html?pr=319882
nixos-unstable
is currently 3 days behind master
from nixvim.
Since I thought it might be of use to others, I fixed the nixpkg dependency overriding problem by removing the home manger module and just used nixvim as a standalone overlay. Getting extra plugins working was a little tricky:
I add it to my overlay and add my extraPluginsSrc vim plugin inputs to extraSpecialArgs. It uses a trick to get all the inputs starting with "vimplugin-", but you can just pass in an attrset manually if you like.
I then build them using the nixpkgs in nixvim
And pass in to extraPlugins
then you can just use
home.packages = [ nixvim ];
from nixvim.
I had same issue with "error: Alias @astrojs/language-server is still in node-packages.nix" just removed "nixpkgs.follows" solved the issue.
Addressed in 8ff21b7
from nixvim.
i have only nixvim.url = "github:nix-community/nixvim";
in my inputs. it has been generated by nix flake init -t github:nix-community/nixvim
i don't see any option where it is specified to be nixvim.inputs.nixpkgs.follows";
still having the same issue.
from nixvim.
I removed the 'follows' line from mine, went to the directory with my NixOS config, and ran sudo nix flake update
, and then ran sudo nixos-rebuild --flake . switch --upgrade
and it built with no issues.
from nixvim.
After removing the
follows
and running bothnix flake update
andnix flake lock
multiple times, I still get the same build error.
If follows
is not having an effect, try overriding your main nixpkgs input (the one that becomes pkgs
in your modules) to point to a nixpkgs without this issue. We're currently locked to 57d6973abba7ea108bac64ae7629e7431e0199b6
.
The upstream PR has made it to nixos-unstable-small
, so that channel may also work (hopefully, anyway).
Is there any information I can provide to try to find a solution to this
I'm curious which installation method you use for nixvim (nixos, hm, darwin, standalone), it may be this determines whether nixvim evaluate using its own nixpkgs input or the pkgs
of a wider module system.
from nixvim.
I'm also seeing this where I got a custom nixvim flake that wraps nixvim this has
nixpkgs.follows = "nixvim/nixpkgs";
And just running nix run .#
works. But if i add it to my nixos config which just have mvim.url = "github:meck/mvim"
(no follow in the input) this error pops up as if it using the general nixos nixpkgs version, nixos-unstable.
from nixvim.
The update has now made it into nixpkgs. Now #1702 is stopping me from building, but this is a separate issue.
from nixvim.
Just curious, is there a reason why setting plugins.lsp.servers.bashls.enable = false;
and/or overriding plugins.lsp.servers.bashls.package
still triggers this issue? I had a quick look at _mk-lsp.nix
and from my understanding package
shouldn't get evaluated if enabled
is false.
from nixvim.
Just curious, is there a reason why setting
plugins.lsp.servers.bashls.enable = false;
and/or overridingplugins.lsp.servers.bashls.package
still triggers this issue? I had a quick look at_mk-lsp.nix
and from my understandingpackage
shouldn't get evaluated ifenabled
is false.
I haven't looked at this specific case, but NixOS modules often evaluate a lot of branches that might not get evaluated in non-module nix expressions. This is done to ensure more parts of your config are valid, even some parts you aren't using.
For instance, lib.mkIf
isn't actually using if then else
, instead it just returns an attrset with a condition attribute and a config attribute. The module system itself then evaluates the config, regardless of condition being successful. It just only gets merged into the final config
if the condition was successful.
from nixvim.
I suspect this might be due to home-manager.useGlobalPkgs = true;
but is breaks too many things for me to confirm this
from nixvim.
Related Issues (20)
- Better `package` option helpers HOT 1
- [BUG] The update CI schedules on forks
- [PLUGIN REQUEST] FeMaco
- [BUG] Alias @astrojs/language-server is still in node-packages.nix HOT 2
- [BUG] flaky codium test in cmp-sources
- [BUG] `disallowedRequisites` is used on a derivation that doesn't support it HOT 2
- [PLUGIN REQUEST] flutter-tools
- [BUG] Error with vscode-langservers-extracted dependent lsp servers HOT 3
- [BUG] Error when lsp html server is enabled HOT 1
- how to lazy: plugins with submodules
- [BUG] enabling some lsp servers fails to build because of `vscode-langservers-extracted` HOT 3
- [BUG] lightline is generating a wrong key name for component_function HOT 2
- [BUG] Conform plugin config using deprecated syntax for stop after first formatter HOT 4
- 'diagnostics' seemingly unavailable under programs.nixvim.* when used with home-manager HOT 2
- [PLUGIN REQUEST] helpview.nvim
- cmp `autoEnableSources` behaviour should be documented more prominently
- [PLUGIN REQUEST] Avante
- [PLUGIN REQUEST] ts-comments.nvim
- [PLUGIN REQUEST] sg.nvim (Cody)
- A flag to enable icon support in telescope
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nixvim.