ehmicky

Memoizing `error.stack` in V8 is not a bug, it is a performance feature, which has been around for many years. Therefore it is unlikely to be removed by the V8...

Yes, that's a good point about this not being only an issue with the automated tests, but a memory leak which could potentially be experienced by users too. `error.stack` memoization...

I can confirm we are planning to provide a way to set inputs through the UI :+1: It looks to me that, since this plugin is generic, most users might...

Caching `.cache` has been reverted since the last comment by https://github.com/netlify/build-image/pull/443 That being said, I am still wondering whether making users chose which paths to cache is better (since it...

Build plugins versions can now be pinned, we've added the feature recently ([documentation](https://github.com/netlify/plugins/blob/main/docs/CONTRIBUTING.md#versioning)) :) > Do you know what would happen if someone would still manually cache something that is...

> Would netlify lock a specific version automatically in this case? It will then behave roughly the same way as when a plugin is installed through the UI, including the...

Hi @pavitra-infocusp, Thanks for reaching out. When I run your first example on Ubuntu 23.10, Node 22.0.0, npm 10.6.0, Execa 8.0.1, I get the following result instead: ```js { command:...

Thanks @lenovouser and @novemberborn!

I think the reason for the current situation was due to implementation details. Namely, both features are implemented using the `PATH` environment variable, so the `nodePath` feature got piggybacked onto...

@pavitra-infocusp Did you end up solving this problem? If so, should we close this issue?