You do not need to load node modules. This defeats the goal of simply pushing git. And you do not want to include node modules in the git repository.
The βsecretβ is to add the dependencies of the node module to your main package.json project, and then add your web jobs to your base project folder with this structure:
App_Data \ jobs \ continuous \ [job name]
The web job in this folder should not have package.json or node modules, because it uses the modules specified in the main package.json project. Its main file should be called "run.js".
I just discovered this today, and youβre ashamed that you need to dig through the entire Internet before you know that you donβt need to manually upload web tasks to the Azure portal. Microsoft, please add documentation for these things for people using node.js. Azure is an awesome platform! But the barrier to entry for Azure with node.js is high because of such things.
See this useful article for more details:
http://blog.amitapple.com/post/74215124623/deploy-azure-webjobs/#.V6JkF7grKUl
source share