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
I'm using essentially vanilla bun + solidstart, and for whatever reason, whenever the .direnv directory is present, it causes bun run vinxi dev (aliased to bun dev) to infinitely use ram and CPU without launching the webserver.
Works with direnv on it's own
Works with direnv+nix-direnv, aslong as .direnv is moved to somewhere outside the project
breaks with direnv+nix-direnv, with .direnv in the default location (project root)
The text was updated successfully, but these errors were encountered:
This sounds like a problem with direnv, bun or solidstart, not with nix-direnv. Nix-direnv doesn't particularly care where your direnv cache is - we just write and read it. I want to say it is likely a problem of creating new shells infinitely and getting caught in the resultant recursive invocation of direnv, but that doesn't explain why direnv itself works with the default cache location. Is there something in this set up that finds scripts and execs them without knowing where they came from?
While I don't think this is a nix-direnv problem, maybe a small reproduction repository will help you isolate the badly behaving software or give us a way we can look over it to help you out?
EDIT: New question: Does this reproduce with node instead of bun?
I'm using essentially vanilla bun + solidstart, and for whatever reason, whenever the .direnv directory is present, it causes
bun run vinxi dev
(aliased tobun dev
) to infinitely use ram and CPU without launching the webserver.Works with direnv on it's own
Works with direnv+nix-direnv, aslong as .direnv is moved to somewhere outside the project
breaks with direnv+nix-direnv, with .direnv in the default location (project root)
The text was updated successfully, but these errors were encountered: