Use `utils.functions.add()`

[netlify]

Use `utils.functions.add()`

[ascorbic]

Yeah. I'm mostly interested in when we can use the private functions directory that @eduardoboucas is working on, and I'm guessing that will also require changes in the helper to specify which one

[ascorbic]

The problem with utils.fucntions.add is that it won't overwrite existing functions, which we need.

[ehmicky]

That's correct, good point.
I'm happy to change utils.functions.add() behavior to allow overwrites, since this seems to make more sense for plugin authors. What do you think?

[eduardoboucas]

Yeah. I'm mostly interested in when we can use the private functions directory that @eduardoboucas is working on, and I'm guessing that will also require changes in the helper to specify which one

This will be possible with netlify/zip-it-and-ship-it#537. The PR sheds some light on what this will look like from the zip-it-and-ship-it side.

Once that lands, we can either make plugins add their own private directories to the config via onPreBuild (e.g. netlify-gatsby-plugin would add .netlify/netlify-gatsby-plugin-functions), or we make Netlify Build look for a generic .netlify/functions-internal (name TBD) directory.

[ascorbic]

Once that lands, we can either make plugins add their own private directories to the config via onPreBuild (e.g. netlify-gatsby-plugin would add .netlify/netlify-gatsby-plugin-functions), or we make Netlify Build look for a generic .netlify/functions-internal (name TBD) directory.

My opinions would be that a shared internal-functions directory would be best, otherwise it will be confusing about priorities for clashing names

[ascorbic]

Closing as we're handling this differently now