Newly created instance does not start (when default blueprint `modules` are configured incorrectly)
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 146
Description
### Current Behavior
Adding a new instance fails to start.
Logs for instance show:
```
15/01/2024 12:22:07 [system] Launcher version: 1.15.0
15/01/2024 12:22:07 [system] Loading project settings
15/01/2024 12:22:07 [system] Updating project dependencies
15/01/2024 12:22:08 [system] [npm] npm
15/01/2024 12:22:08 [system] [npm] ERR! must provide string spec
15/01/2024 12:22:08 [system] [npm]
15/01/2024 12:22:08 [system] [npm] npm ERR!
15/01/2024 12:22:08 [system] [npm] A complete log of this run can be found in: npm
15/01/2024 12:22:08 [system] [npm] ERR! C:\Users\Stephen\npm-cache\_logs\2024-01-15T12_22_08_079Z-debug-0.log
15/01/2024 12:22:08 [system] Unable to install or update packages
```
Settings for instance show:

---
NOTES:
* At first, I had failed to pull launcher (was on previous ver 1.14). Updated to latest HEAD - same issue
* Upgraded node to 18 LTS latest, pulled all repos, rebuilt node_modules - same issue
### Expected Behavior
* Module list should not have `modules: []`
* Instance should start
### Steps To Reproduce
Running latest main (HEAD) from all repos, create a new instance.
### Environment
- Instances are running Node-RED stack 3.1.3
- FlowFuse version: 1.15_git
- Node.js version: 16.x AND 18.19.x (LTS)
- npm version:
- Platform/OS: Windows 11
- Browser: Chrome latest
### Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Contributor guide
Assessment
This issue has not been assessed yet.