Andreas Rammhold
Andreas Rammhold
Mhm, that is a bummer. I'll have to think about the alternatives for this. There was always the path of pre-populating a cache directory that NPM would then pick sources...
The problem with this remains the same: we occasionally have to patch scripts while npm does it's thing as a dependant package might execute a script to e.g. compile native...
I just tried something like your proposal on newer npm and I was greeted with: ``` npm WARN old lockfile The package-lock.json file was created with an old version of...
> I am sorry, but I am not sure how the error you are getting is related to our discussion. > > ``` > npm WARN old lockfile The package-lock.json...
I don't think that updating dependencies with symlinked node_modules is currently possible for all the reasons you've mentioned. There in no feature request on the NPM side just yet as...
IMO just having `${year].nixcon.org` is fine. It allows us to change the entire technology stack over the years without having to migrate content that someone 10y ago wrote in some...
We can get a list of maintainers for files/modules via: ``` nix-instantiate --eval '' --arg configuration '{}' -A config.meta.maintainers --strict --json ``` (cc @Infinisil)
You might not always want to build it or at least have a blacklist? I think building chromium would waste a lot of cpu cycles with probably low benefit?
I am seeing the same error. The `permit_join` command succeeds and then no new devices can be discovered. ``` Feb 25 10:58:40 crappy x[7903]: 2021-02-25 10:58:40 DEBUG (MainThread) [zigpy_deconz.api] Command...