ehmicky

Closing in favor of https://github.com/netlify/pod-workflow/issues/312

Re-opening as it appears that the problem is not connected to what was mentioned in https://github.com/netlify/pod-workflow/issues/312 Namely, it appears that there is a mismatch between `@netlify/build`'s version (`12`) and any...

Hi @juanpprieto, Unfortunately, this is not currently possible. `netlify.toml` itself is read at the very beginning of the build, much before `@netlify/build` starts and before `npm install` is performed. This...

> I didn't see an option for managing plugins. Is this the case? Yes, you're correct, `plugins` is one of the few properties not supported yet. Modifying plugins inside plugins...

Thanks for explaining your use case, this helps a lot and makes lots of sense. Small side note: at a higher-level, I am wondering if account-level build settings would help...

Thanks for the additional feedback. The setup you are describing seems key to being able to provide any managed Netlify agency product offering. This definitely is a must-have from an...

> Yes, this was the plan with the node --eval "require('@myorg/netlify-toml')". i.e so we could control config versions via this "netlify-toml" package. I am wondering whether your idea might share...

I was going to suggest exactly this! :) From a pure implementation standpoint, this solution would also be more lightweight. Account-level build settings would be very useful, but we would...

Great! Thanks for sharing all that feedback. :heart: I've just shared this feature request with the team and we will be exploring it further as part of another feature coming...

Hi @jcayzac, This sounds good. Most of this would need to be implemented in the `build-image` (https://github.com/netlify/build-image/issues/447), not `@netlify/build` though. With the exception of [this file](https://github.com/netlify/build/blob/1d89e3cfd3ce02297815fab3afbbc27f3b9e27f8/packages/build/src/install/main.js#L18) which is used only...