Scott Bender - Node-red is broken with main bra...
Node-red is broken with main branch. Have not figured out yet what changed.
This is with node-red 3.x and 4.x
17 Replies
@Teppo Kurki this is becausw of https://github.com/SignalK/signalk-server/commit/29cfc73018e49603b171322e441414f7bb726224
GitHub
chore(deps): bump body-parser from 1.20.3 to 2.2.0 · SignalK/signa...
Bumps body-parser from 1.20.3 to 2.2.0.
- Release notes
- [Changelog](https://github.com/expressjs/b...
node-red works if I revert
any ideas as to why exactly? @Brandon Keepers
Sorry, I signed off on that PR after looking at the changelog. I'll dig in
node-red code is
guessing they removed/changed
readable
ironic, latest recent commit on node-red repo: https://github.com/node-red/node-red/commit/ba0299abf92c31288f94e15122762b7ba1da8001
So node-red is using body-parser 1.20.3 internally, so must be some kind of conflict mixing versions
well, that may not be released
and anyway . we are still on node-red 3.1
Right, but they tried to update to body-parser 2 and their tests were failing, so they reverted it
ah, ok
we need to revert too
Yeah. I'm going to keep digging for a minute and see if I can fix the node-red issue with body-parser 2, but reverting is probably the easy route for now
specially if we did not have any specific reason to go to v2?
No, nothing specific. Just working on updating dependencies because the debt starts to stack up
yeah, that's a tough one, because we can't test everything
of course, that's the case with anything we change
Yeah, I was thinking about that. I think there should be a sanity test that has the top ~N plugins installed and runs some very basic integration tests.
one would need to fire some http requests to N-R to catch this one, probably? so it gets complex pretty fast
but i am not disagreeing
yep
for sure
No obviously solutions immediately, so reverting for now: https://github.com/SignalK/signalk-server/pull/1960