Failed to deploy - u[e].files.forEach is not a function

[cameronk]

When running the deploy script, I get this error:

...
Start Folder: shared
Start catalogDependencyFiles
Start updateIndex
Start updateIndex
Start updateIndex
Start updateIndex
start CreateDependencyFileJS
FAILURE!
{"success":false,"action":"prepWork","error":{"message":"u[e].files.forEach is not a function","object":{}}}

I believe it comes from this line in the deploy script.

In my project I have a "shared code" directory that shares some utilities between my various Azure functions. The error seems to occur a when processing that directory.

I'm also a bit confused about project structure - should I define a package.json (and my function dependencies) on the function level or the project level?

[securityvoid]

@cameronk Code assumes that your git repo matches the Azure Functions folder structure. As a result you've got your host.json at the base, package.json at the same level for all your functions, and then each function with its own folder. In that folder is the function.json, and the main index.js

Is the code you're running this on public that I could pull and take a look at it? I've run this successfully on 3-4 projects now, but I don't know of many people using this beyond me. As a result I may somehow make some assumptions about folder structure that are not required.

I will say that at this point, I've moved most of my stuff over to my refactor of this code in packgit. No matter how much I optimized a pure deploy script, it took at least 4-5 minutes to deploy for a medium sized project. That was too long for my waiting.

With Packgit, all the Webpacking is done locally and its put into its own branch in Git. So far, its been pretty rock solid for me.