RED.events warning persist.js

[NietGiftig]

Updated Node-red to 1.2.1, updated all nodes with update message showing.
When I do a deploy I get now always 2 warnings in the debug screen.
"[RED.events] Deprecated use of "nodes-started" event from "/home/pi/.node-red/node_modules/node-red-contrib-persist/persist.js:164:20". Use "flows:started" instead."

[nicedevil007]

Same here, any suggestions / fixes?

[sniicker]

Same here, pls help

[sniicker]

did anyone try a earlier version?

I tried Version 1.0.1 - 1.1.1

The same on all versions
My NodeRed Version is 1.2.2

[sniicker]

There is a little workaround.

• go to the folder where the package is installed
  for me ( .....node-red\node_modules\node-red-contrib-persist
• Make a copy of the File persist.js and give it another name
• open the original file and search for "nodes-started" and replace it with "flows:started"

Restart NodeRED and see there is no error any more

Pls @DeanCording check your Code THX

Nice Greatings

[sniicker]

But this is another info i get:
(node:15184) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 flows:started listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit

this info comes with or without the above workaround.

[philosoma]

• open the original file and search for "nodes-started" and replace it with "flows:started"

I've done this, error goes away, but it causes the charts to go wrong and become empty.

[sniicker]

@DeanCording pls help

[emc02]

got the warning too, please fix this with next version!
Everything else works perfect for me! Thanks for that!

[Paul-Reed]

There are 2 nodes-started that need changing to flows-started, then it works ok.

[agenteDserrano]

same here

[bikeymouse]

I also ran into this error and confirm that the fix works, so thanks for the workaround!
@DeanCording / @ StephanStS : it has been some while since a last update ;-) Perhaps this can be included?

[UNOPARATOR]

Just created a PR ( #12 ) for this issue.

[bikeymouse]

Thanks, great!

Just a check: I see that you replaced "nodes_started" to "flows-started" in the code, although the fix mentioned here replaces this with "flows:started". Is both correct?

[UNOPARATOR]

Thanks, great!

Just a check: I see that you replaced "nodes_started" to "flows-started" in the code, although the fix mentioned here replaces this with "flows:started". Is both correct?

I guess you're right, I mistakenly made my changes based on @Paul-Reed's comment, but now that you mentioned it, previous comments state the same as what you mentioned above. I'll check and update my PR accordingly. But we'll never know if it will ever be merged ;)

Edit: Just updated my PR, thanks to @bikeymouse for his/her eagle eyes. 🥇

[arnljot]

There is a little workaround.

This is not a workaround. This is the fix for the deprecated API usage in the component. You should make a pull request with this fix.

[UNOPARATOR]

There is a little workaround.

This is not a workaround. This is the fix for the deprecated API usage in the component. You should make a pull request with this fix.

It has been waiting to be merged since May, 3rd: #12

[rhurup]

Updates?