[Hooks] Evolving the types about azure-functions-nodejs-worker HOT 3 CLOSED

Discussed this one a bit during today's sync. We don't want people using the "@azure/functions-core" api directly. It's clunky to use, it's slow for us to roll out changes, and we have to be super careful about backwards compatibility. There's quite a few hooks requests (more than we have time for) and we want to prioritize the work on the npm package. Closing this issue in favor of Azure/azure-functions-nodejs-library#7

from azure-functions-nodejs-worker.

I think that for any of the work in the library to be done, this will need to be tackled as the library package will need these types and at present they are inflexible and make creating abstractions difficult.

from azure-functions-nodejs-worker.

Discussed a bit offline. Current plan is to implement all of this stuff in the library package, not the worker. I don't think it'll be too inflexible/difficult, but we can always revisit if @hossam-nasr finds otherwise when working on the prototype.

Also when I say "library" package I'm talking specifically about @azure/functions. Aaron brought up that there could be other libraries that want to reference @azure/functions-core instead of @azure/functions. We want to see what people think of the support in @azure/functions before we go down that road, though

from azure-functions-nodejs-worker.