# 🎉 Node-RED 2.0.0-beta.1 Released

**URL:** <https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990>\
**Category:** News\
**Created:** [10 June 2021 15:21 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990 "2021-06-10T15:21:18Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 June 2021 20:24 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/22 "2021-06-10T20:24:19Z")

</div>

> [@Steve-Mcl](#):
>
> Should I just keep updating branch as issues are found and fixed?

Yes. As I said, we won't merge the PR until we're all agreed, but it gives us something to have in the 2.0 project plan so it doesn't get forgotten.

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [10 June 2021 20:42 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/23 "2021-06-10T20:42:05Z")

</div>

Oops, I should have done that instead of just posting here. Sorry about that, and thanks @Steve-Mcl

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 June 2021 20:43 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/24 "2021-06-10T20:43:34Z")

</div>

> [@Botched1](#):
>
> , I should have done that instead of just posting here

Posting here is the right thing to do for the beta so we have one place where issues are gathered.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 June 2021 20:52 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/25 "2021-06-10T20:52:45Z")

</div>

This is bad timing, I am away from home so I won't be able to play till the rest of you have had all the fun sorting out the wrinkles. ☹

---

<div class="post-metadata">

**Author:** ![ghayne](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ghayne/32/39_2.png) [@ghayne](https://discourse.nodered.org/u/ghayne)\
**Post date:** [10 June 2021 21:08 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/26 "2021-06-10T21:08:50Z")

</div>

Installed fine and running without issues on a Zero W Buster here.

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [10 June 2021 21:21 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/27 "2021-06-10T21:21:06Z")

</div>

As I understood from previous threads of monaco code editor, there is or will be some options for monaco to adjust at settings.js but there is no hints like all other setting options have. Would be helpful if can be added.

Many thanks. Great work.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [10 June 2021 21:25 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/28 "2021-06-10T21:25:30Z")

</div>

you mean you want docs before release... wow that would be a first 😉  
though the new settings file does have some clues re theme, fonts etc, and does include a link to [IStandaloneEditorConstructionOptions | Monaco Editor API](https://microsoft.github.io/monaco-editor/api/interfaces/monaco.editor.istandaloneeditorconstructionoptions.html)  
which should be enough to keep you amused for a while.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 June 2021 21:33 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/29 "2021-06-10T21:33:59Z")

</div>

The new default settings file does include a link to the Microsoft docs.

> <https://github.com/node-red/node-red/blob/4acb66fb7a4c50ba237248ac61b20f0472526d08/packages/node_modules/node-red/settings.js#L357>

I'm not sure what else we'd want to add.

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [10 June 2021 21:49 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/30 "2021-06-10T21:49:06Z")

</div>

Yeah, sorry. My fault. The new settings file of course has all what is needed. Having too many VSCode-s running and then steering completely wrong file just fooled me completely.

---

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [11 June 2021 07:37 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/31 "2021-06-11T07:37:04Z")

</div>

I think I'm hitting a bug in HTTP Request node, without using a proxy so it shouldn't be part of the known issue.

I'm using basic authentication in a flow that queries an API endpoint (confirmed as working with the same username/password combination in `1.3.5`) this is what I'm seeing in the console:

```auto
11 Jun 07:26:13 - [error] [http request:Harvest API Daily] HTTPError: Response code 401 (Unauthorized)
    at Request.<anonymous> (/usr/src/node-red/node_modules/got/dist/source/as-promise/index.js:117:42)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

```

I'm running the beta in a container on a raspberry pi, using a custom built image (as I always do).  
the Node.js version used is: `Node.js version: v12.22.1`

Everything else appears to be working as it did using the non beta version.

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [11 June 2021 08:28 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/32 "2021-06-11T08:28:25Z")

</div>

Just to report... upgraded to 2.0.0-beta-1 on a RPi-4B, Buster OS - no problems at all.

I copied the default settings.js file (in Nick's link above) to a new file in my Node-RED area, then swapped the files around so I had the new file and also retained the old file (just in case I needed to do a revert).  
I then edited the line... ` lib: "ace:` to `lib: "monaco"` and did a reboot. Really nice editor. Thanks Steve.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [11 June 2021 08:51 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/33 "2021-06-11T08:51:30Z")

</div>

Re Monaco snippets - currently when you use node.warn or node.error it auto selects the complete string including quotes for replacement  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/7/67e78562376825a1a59e4ce7eef51bf560214188.png)  
It could (eg like the node.status) just highlight the text between quotes  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/d/2d770728218df86ee93f8f6810f8f41fa1c0d5b5.png)  
So then you don't have to re-type the quotes... I think this is more natural - but...

Of course you may want to insert a variable instead of text - but I think it's a better hint that it should be text if it defaulted to just replacing the text rather than the complete string.

What do others think ?

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [11 June 2021 09:17 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/34 "2021-06-11T09:17:59Z")

</div>

Juzam,

Can you supply some more details about this please, testing against a local basic auth server is working.

How are you setting the username/password?

---

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [11 June 2021 09:29 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/35 "2021-06-11T09:29:17Z")

</div>

@hardillb I'm setting the credentials in the node properties window like this:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/6/d66f23c6ca9d048d22a181ad77d8081e0c981f02.png)

the flow is basically an Inject Node, a function node that sets the Headers:

```auto
msg.headers = { "Accept": "application/json" }
return msg;

```

that goes to the http request node, nothing fancy here I suppose.

The other thing that comes to mind is that the URL is https but I didn't check the `Enable secure (SSL/TLS) connection`

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [11 June 2021 09:38 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/36 "2021-06-11T09:38:12Z")

</div>

Can you let me know what API you are hitting. Is it something I could get a trial account for to test?

---

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [11 June 2021 09:46 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/37 "2021-06-11T09:46:18Z")

</div>

Yes, it's not a problem. I'm hitting the Harvest API v1 (which is discontinued but still works for legacy apps) this endpoint specifically [https://help.getharvest.com/api-v1/timesheets-api/timesheets/retrieving-time-entries/](https://help.getharvest.com/api-v1/timesheets-api/timesheets/retrieving-time-entries/). You can get a free trial without a credit card as per: [Harvest App Pricing](https://www.getharvest.com/pricing)

Thank you for taking the time to look into this.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [11 June 2021 10:06 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/38 "2021-06-11T10:06:28Z")

</div>

> [@dceejay](#):
>
> What do others think ?

Just as it is now IMO.  
As you have said, users may wish to insert a variable, which if the quotes remained would mean further editing, or result in an error.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [11 June 2021 10:21 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/39 "2021-06-11T10:21:14Z")

</div>

I can't see how to get the `YOURACCOUNT` part of URL for the v1 API

I assume they have disabled that to prevent people building new projects with the v1 API since it's deprecated

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [11 June 2021 10:43 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/40 "2021-06-11T10:43:49Z")

</div>

OK worked it out, it's the `@` in the username that got doesn't like it

> <https://github.com/sindresorhus/got/issues/1169>
>
> \#### Describe the bug
> 
> \#### Actual behavior
> 
> When I use the username/passwor…d with got, It seems that the combo 'username:password' is encoded with encodeURI() before to be encode in base64 for the basic auth. This first encoding is not necessary due to the base64 encoding and brings problems. So when the encodeURI() change a value like '@' to '%40', the basic authentification doesn't work.
> 
> \#### Expected behavior
> 
> Just encode the combo 'username:password' with base64 encoding.
> 
> \#### Code to reproduce
> 
> \`\`\`js
> const got = require('got');
> 
> (async () =\> {
> const response = await got.head("http://example.com/", {username: "user@", password: "password@"});
> console.info("Response:", response.client.\_httpMessage.\_header);
> }) ();
> \`\`\`
> We see that the Authorization header is invalid
> 
> \#### Checklist
> 
> \- \[X\] I have read the documentation.
> \- \[X\] I have tried my code with the latest version of Node.js and Got.

---

<div class="post-metadata">

**Author:** ![RoganFPS](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/roganfps/32/3208_2.png) [@RoganFPS](https://discourse.nodered.org/u/RoganFPS)\
**Post date:** [11 June 2021 12:54 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/41 "2021-06-11T12:54:21Z")

</div>

I hope 2.0.1 includes colour themes for monoco @Steve-Mcl 👏

[Previous page](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990.md?page=1)

[Next page](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990.md?page=3)