FlowFuse / FlowFuse/flowfuse

Upgrading from a old stack (unknown which) can lead to Flows not starting

Open
#3,045 1 comment 0 reactions 0 assignees View on GitHub
needs-triage
Dominant language
JavaScript
Stars
400
Forks
89
Avg merge
1d 20h
Merged PRs (30d)
149

Description

### Current Behavior

upgrade to 1.13.1 based stack leads to message about missing @flowforge/nr-project-nodes (0.1.1) package in Node-RED startup logs and a failure to start.

Might need logic to update the discovered nodes list if upgrading stack versions to one which now contains @flowfuse/nr-project-nodes

Also I could not find @flowforge/nr-project-nodes on npmjs.com

When I logged into the instance, the new project nodes were present so the flows just needed starting.

### Expected Behavior

Node-RED to start and use new nodes

### Steps To Reproduce

_No response_

### Environment

- FlowForge version: 1.13.1
- Node.js version: 16.x
- npm version: 8.x
- Platform/OS: k8s/Linux
- Browser: NA

### Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.