🎉 Node-RED 1.0.0-beta.2 released

News
21

All reported issues fixed:

  • :white_check_mark: TypedInput is broken for Boolean type
  • :white_check_mark: Pinned Debug message background
  • :white_check_mark: TreeList Children api
  • :white_check_mark: Status icon not being drawn

Thanks for the feedback - keep it coming.

3 Likes
22

I am not sure if I am doing something wrong or this could be really something to look at...

1 - Build the most bassic flow
2- try to export to library

Nothing happens when clicking buttom Export to library

I tried in a windows machine as well as on a Raspberry.

23

Any errors in the browser log?

24

Same happened to me and then I realised we have to click on local before clicking on export

image
image.png763×633 13.7 KB

1 Like
25

@knolleary, yes Nick. See below:

t-02
t-02.png967×267 19.4 KB

but it works as @cymplecy well noted (tks Simon).

26

Fixed:

  • :white_check_mark: Library browser now auto-selects first entry in the list to avoid that error
3 Likes
27

Hi Nick,
Just wondering when you say the various 'issues' have been 'fixed'...
Do I have to wait for the next beta release to get them??

28

Don't know if it has been fixed together with "Library browser now auto-selects first entry" fix so

Export editor if trying to Download the flow, error in browser and no functionality.

error

image
image.png701×595 22.1 KB

29

Thanks for reporting - fixed:

  • :white_check_mark: Library export download button
30

Yes. You don't get the fixes until we release them. We'll be refreshing the beta once a week (or there abouts).

31

I've upgraded to Node-RED v1.0.0-beta.2
I am seeing strange dropdown rendering behavior using the UDP in / out and TCP in/out/request nodes. I tested my local flow in both Firefox and Chrome and see the blank dropdown fields in both browsers. I have reinstalled node-red-bluemix-nodes v1.1.10 and still see the issue.

udp-node-rendering
udp-node-rendering.png853×472 19.5 KB

32

Thanks for reporting @johnwalicki. That is odd; I don't think we've seen that with other modules that provide their own i18n messages. Will investigate.

33

do we have udp and tcp on bluemix ? If so they would be their own nodes so may never have been i18n

34

Yes - The UDP / TCP nodes render correctly on IBM Cloud (running Node-RED v0.20-5). I have not tried to install Node-RED v1.0 Beta on IBM Cloud yet.

35

Does that mean you have installed node-red-bluemix-nodes locally? That module is not really intended for local use as a lot of the nodes assume they are running in the IBM Cloud environment. Did the module work locally prior to 1.0?

36

Yes, node-red-bluemix-nodes works locally. I only mention it because that's what provides the UDP and TCP nodes. I need the UDP node to control the drone. I can roll back to Node-RED v0.20 to test again.

37

Well no - the core node-red palette includes UDP/TCP nodes. You do not need bluemix-nodes installed to have them available. The bluemix-nodes module provides custom versions of those nodes for the IBM Cloud environment - and the bluemix-settings.js file is configured to block loading of the core tcp/udp nodes so they don't clash.

38

Hi i installed node-red version v 0.20.5 on a raspberry pi 3b+ with the latest raspbian stretch desktop
with this command:
bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

When i enter to upgrade to the latest beta:
sudo npm install -g --unsafe-perm node-red@next
i get: sudo: npm: opdracht niet gevonden

i read that i had to specify @next, do i have to type something else, so what?

39

Interesting! I didn't know there were two versions of the UDP/TCP nodes. Independent of my v1.0 bug report, on my local instance, I'll flip back to the core Node-RED palette nodes. Regardless, it looks like a rendering / i18n bug in node-red-watson-nodes with Node-RED v1.0

40

That says that the npm command isn't found which is a bit odd if the bash install script ran OK.
what does node -v report ?