tgunn

Is there a way we can add flake support in an effort to streamline the reproducibility of extra-container? Ideally I see 2 types of outputs from this repository: NixOS and...

OpenGL ES 3: Fail to start on aarch64: [glfw error 65543]

39

**Describe the bug** Fails to start **To Reproduce** `$ kitty` **Expected behavior** Startup **Screenshots** ``` [175 14:38:59.616720] [glfw error 65543]: EGL: Failed to create context: Arguments are inconsistent [175 14:38:59.621982]...

yarn-lock: using relative path for "file:" in a workspace's subpackage probably won't match yarn.lock's reference to it

2

I made an example repository: https://github.com/tgunnoe/d2n-workspace-package-files-example/ [In a workspace subpackage's package.json, a dependency referencing a relative path](https://github.com/tgunnoe/d2n-workspace-package-files-example/blob/master/packages/core/package.json#L7) will not find what yarn resolves it as [in its own yarn.lock](https://github.com/tgunnoe/d2n-workspace-package-files-example/blob/master/yarn.lock#L25) The...

I've encountered this error or similar several times in the past: ``` error: attribute '0.6.8' missing at /nix/store/h450vx8mjsx1ijyl4nqcc5bsjci088n6-source/src/lib/simpleTranslate2.nix:169:15: 168| children = 169| depGraphWithFakeRoot."${node.name}"."${node.version}"; | ^ 170| (use '--show-trace' to show...

nix run .#package.resolve does not work if packagesDir is defined

1

First, If you try to define `config.packagesDir` without the directory already existing (in this case, a dir name same as default-- but any name produces the same errors), you get:...

Look for hoisted dependencies in yarn monorepos

4

Some monorepos have [hoisted dependencies](https://yarnpkg.com/advanced/lexicon#hoisting) and require many dream2nix injections. I would say dream2nix can look upwards in a monorepo for the root `package.json` after it cannot locate missing dependencies.

fix: nodejs: strict-builder: patch shebangs

6

For the scenario where the installed `node_modules` were used for building (nestjs in my situation), the shebangs were not patched for build time in the strict-builder. That lead to `no...