floco
floco copied to clipboard
aakropotkin
Using Nix to put NPM and Yarn in a coffin
Its is currently very hard to take one module and re-use it in isolation. For example if you just wanted to take the 'plock2pdefs' module you also have to import...
`nice-napi` is an example.
After executing `floco translat -ptj`, the pdef.json file contained the following entry for the top-level package: ```json [...] "fetchInfo": "path:.", [...] ``` On a `nix build` this leads to the...
example override: ```nix { floco.pdefs.prettier."2.8.7".fetchInfo = l.mkForce { path = "${config.nodejs-floco.source}"; }; } ``` This leads to an error like: ``` error: access to absolute path '/nix/store/kcb6fw0g6swnfyacb0y1fn2dzlmdzhfc-source/package.json' is forbidden in...
This is a "maybe aren't working". I noticed when created a new test case that `foverrides.nix` containing `config.floco.packages."@floco/phony"."4.2.0".source = ...;` wasn't being used by `prepared`. I tried this with `mkForce`...
The following two invocations of floco lead to different results, which is not intuitive: This command ignores `devDependencies` ```command floco translate -- -ptj $source ``` This command respects `devDependencies` ```command...
Default fields aren't being applied, this specifically effects `depInfo.*.dev` values.
A small optimization, but every bit counts with an operation like this.
`mkTreeInfoHoisted` is unreasonably slow to the point of being unusable for any project larger than ~150 modules. A rough list of things that could be optimized here are: 1. `subScopeHoisted`...