New node to be added to https://flows.nodered.org:
Here is an example for using Cheerio with a Node-RED function. It should be easily adapted to your node since the example simply makes Cheerio available to a function node manually.
And the built in HTML node uses cheerio also.
Thanks for the hint, this option was already known to me, but I wanted to have a palette based only install of a cario node, as it is not always possible to fiddle with settings.js and add globals. In my use case I run somewhere node-red based on a docker container and can't change local files just use web access alone.
As for the HTML node, thx, didn't know that, cool. Still doesn't solve my problem in being as flexible as a function node. Would be really cool to have the option to change globals at runtime or with a deploy. And expose them directly without fiddling around the global.get()... in function node. Or have some sort of Node-Red config that can be edited from Web-UI to achieve something similar.
In the end, does this mean my node is not being accepted?
Should be fine as long as packaged properly. But we have been having problems with npm not automatically indexing them properly recently and both Nick and I are on vacation so can’t kick manually at the moment.
(Just pointing out that very similar functionality already exists so may not be necessary. Always good to propose/discuss on the forum before writing loads of code
(And better config options are on the todo list)
And for better config options being on todo list
I get the reasons and it makes for a neat solution anyway.
This is easily done. Just put a suitable inject flow on the first tab. Make it fire on load. I do this with a number of key globals. The advantage of the settings file of course is that it can't be changed by an admin user unless they have access to the file system. So it is good to have both options.
It is an open source system so nobody can block you