Allow specifying source folder and package.json location seperately

[Weeknie]

In our project, we use the following structure (only relevant files are shown, e.g. README and others are excluded):

repository/
├── test/ (unit tests)
├── lib/
│   ├── app1/
│   │   ├── function.json
│   │   └── index.js
│   └── app2/
│        ├── function.json
│        └── index.js
├── .deployment
├── deploy.cmd
└── package.json

As you can see, we keep our function app code in a lib folder, to seperate them top-level from our test code. However package.json is in the root level, since it specifies both dependencies of the actual code and additional dependencies for test code.

However, the generator, as I understand it, only accepts the package.json file to be at the same level as the function app folders (i.e. app1 and app2)

I would like to suggest the possibility to add a seperate location to copy package.json from, or something along the lines. It would result in an extra xcopy command, alongside the command to copy the functionapp root (i.e. the {sitePath} folder)

[davidebbo]

@Weeknie note that kuduscript is just a starting point, and cannot support every possible scenario. Have you tried using a custom deployment script to do exactly what you want?

[Weeknie]

@davidebbo I did, and the script works wonderfully. My apologies if this suggestion was too specific/too soon.

I just think that the structure we use is quite general (it's used for most node modules, kuduscript itself uses it), and more people might run into this. That is the reason I suggested it, feel free to decline :)

[davidebbo]

@Weeknie understood. Let's keep this open and see if others run into this as well.