Merge branch 'node-red:master' into master

Author: rvangeijtenbeek

README.md

@@ -23,6 +23,6 @@ First time you run jeykll you need to do bundle install 1st for the dependencies
 
     cd node-red.github.io
     bundle install
-    jekyll serve -w
+    bundle exec jekyll serve -w
 
 Once the site is built and running you can preview it at [`http://127.0.0.1:4000/`](http://127.0.0.1:4000/).

_includes/footer.html

@@ -25,6 +25,7 @@
                 <li><a href="https://twitter.com/nodered">Twitter</a></li>
                 <li><a href="https://discourse.nodered.org">Forum</a></li>
                 <li><a href="/slack">Slack</a></li>
+                <li><a rel="me" href="https://social.nodered.org/@nodered">Mastodon</a></li>
             </ul>
         </div>
     </div>

docs/api/ui/typedInput/index.md

@@ -16,7 +16,7 @@ chosen, including options for string, number and boolean types.
 - [Events](#events)
 - [Types](#types)
 - [Examples](#examples)
-
+- [Runtime handling of typed values](#runtime-handling-of-typed-values)
 
 <div class="widget">
     <div style="clear:both">
@@ -125,6 +125,34 @@ $(".input").typedInput({
 });
 ```
 
+When used in a Node-RED node, this value can be stored as a node property by adding
+an entry for it in the node's `defaults` object. This ensures the type is saved
+along with the value in the node configuration.
+
+```html
+<div class="form-row">
+    <label>Example:</label>
+    <input type="text" id="node-input-myField">
+    <input type="hidden" id="node-input-myFieldType">
+</div>
+```
+```javascript
+RED.nodes.registerType('example', {
+    defaults: {
+        myField: { value: "" },
+        myFieldType: { value: "str" }
+    },
+    ...
+    oneditprepare: function () {
+        $("#node-input-myField").typedInput({
+            typeField: "#node-input-myFieldType"
+        });
+    }
+})
+```
+
+
+
 ### Methods
 
 <a name="methods-type"></a>
@@ -369,6 +397,52 @@ $("#node-input-example5").typedInput({type:"fruit", types:[{
 <div class="red-ui-editor"><input type="text" id="node-input-example5"></div>
 
 
+### Runtime handling of typed values
+
+Due to the way the `typedInput` enhances a regular HTML `<input>`, its value is
+stored as a string. For example, booleans are stored as `"true"` and `"false"`.
+
+When stored as node properties, it is necessary for the runtime part of the node
+to parse the string to get the typed value.
+
+A utility function is provided to handle the built-in types provided by the TypedInput.
+
+```javascript
+RED.util.evaluateNodeProperty(value, type, node, msg, callback)
+```
+
+Property | Type    | Required | Description
+---------|---------|----------|-------------
+`value`  | string  | yes      | The property to evaluate
+`type`   | string  | yes      | The type of the property
+`node`   | Node    | yes, for certain types | The node evaluating the property
+`msg`    | Message Object | yes, for certain types | A message object to evaluate against
+`callback` | Callback | yes, for `flow`/`global` types | A callback to receive the result
+
+For most types, the function can be used synchronously without providing a callback.
+
+```javascript
+const result = RED.util.evaluateNodeProperty(value, type, node)
+```
+
+For `msg` type, the message object should also be provided:
+
+```javascript
+const result = RED.util.evaluateNodeProperty(value, type, node, msg)
+```
+
+To handle `flow` and `global` context types, the node needs to be provided as well as
+a callback function due to the asynchronous nature of context access:
+
+```javascript
+RED.util.evaluateNodeProperty(value, type, node, msg, (err, result) => {
+    if (err) {
+        // Something went wrong accessing context
+    } else {
+        // Do something with 'result'
+    }
+})
+```
 
 
 <script src="/js/jquery-ui.min.js"></script>

docs/faq/node-versions.md

@@ -5,16 +5,15 @@ title: Supported Node versions
 slug: node versions
 ---
 
-Node-RED currently recommends **Node 14.x LTS**.
+Node-RED currently recommends **Node 16.x LTS**.
 
 Version    | Support Level   | Notes
 -----------|-----------------|------
- < 8.x     | *Unsupported*   |
- **8.x**   | *Supported*     | Node-RED 1.x or earlier only
- **10.x**  | *Supported*     | Node-RED 1.x or earlier only
- **12.x**  | *Supported*.    |  
- **14.x**  | **Recommended**   |  
- **16.x**  | Supported       |  
+ < 10.x    | *Unsupported*   | Node-RED 1.x or earlier only
+ **12.x**  | *Supported*     | Node-RED 2.x or earlier only
+ **14.x**  | Supported       |  
+ **16.x**  | **Recommended** |  
+ **18.x**  | Supported       |  
 
 We try to stay up to date with Node.js releases. Our goal is to support
 the [Maintenance and Active LTS releases](https://nodejs.org/en/about/releases/).

docs/getting-started/raspberrypi.md

@@ -25,7 +25,7 @@ to review the contents of the script first, you can view it [on Github](https://
 bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
 ```
 
-There are extra parameters you can pass to the script. Add `--help` to the above command to see them.
+There are extra parameters you can pass to the script. Add ` --help` to the end of the above command to see them.
 
 <div class="doc-callout">
 <div style="float: left; margin-right: 10px; margin-bottom: 30px;">
@@ -40,7 +40,7 @@ first to ensure npm is able to fetch and build any binary modules it needs to in
 This script will:
 
  - remove the existing version of Node-RED if present.
- - if it detects Node.js is already installed, it will ensure it is at least v12. If less than v12 it will stop and let the user decide whether to stay with Node-RED version 1 - or upgrade Nodejs to a more recent LTS version. If nothing is found it will install the current Node.js LTS release using the [NodeSource](https://github.com/nodesource/distributions/blob/master/README.md) package.
+ - if it detects Node.js is already installed, it will ensure it is at least v14. If less than v14 it will stop and let the user decide whether to stay with Node-RED version 1 - or upgrade Nodejs to a more recent LTS version. If nothing is found it will install the Node.js 16 LTS release using the [NodeSource](https://github.com/nodesource/distributions/blob/master/README.md) package.
  - install the latest version of Node-RED using npm.
  - optionally install a collection of useful Pi-specific nodes.
  - setup Node-RED to run as a service and provide a set of commands to work with
@@ -50,10 +50,12 @@ This script will:
 <div style="float: left; margin-right: 10px;margin-bottom: 40px;">
 <img src="/images/logos/raspberrypi.svg" height="30">
 </div>
+
 Node-RED has also been packaged for the Raspberry Pi OS repositories and appears in their
 list of 'Recommended Software'. This allows it to be installed using
 <code>apt-get install nodered</code> and includes the Raspberry Pi OS-packaged version
 of Node.js, but <em>does not</em> include <code>npm</code>.
+
 <p><b>Note</b>: at this time the default node.js included with RaspiOS Bullseye is still v12. This means that the latest Node-RED version that can be installed is the 2.x branch. While using these packages is convenient at first, we <b>strongly recommend</b> using the install script above instead.</p>
 </div>
 

docs/user-guide/nodes.md

@@ -42,6 +42,7 @@ If you are looking at intervals greater than one day - consider using a schedule
 The `interval between times` and `at a specific time` options use the standard cron system. This means that 20 minutes will be at the next hour, 20 minutes past and 40 minutes past - not in 20 minutes time. If you want every 20 minutes from now - use the `interval` option.
 
 *Since Node-RED 1.1.0*, the Inject node can now set any property on the message.
+
 ***
 
 <img alt="Debug node" style="float: right; margin-top: 20px;" src="/docs/user-guide/images/node_debug.png" width="169px">

docs/user-guide/runtime/securing-node-red.md

@@ -197,7 +197,7 @@ The `strategy` property takes the following options:
  - `label`/`icon` - used on the login page. `icon` can be any FontAwesome icon name.
  - `options` - an options object passed to the passport strategy when it is created.
    Refer to the strategy's own documentation for what it requires. See below for a
-   node on the `callbackURL`.
+   note on the `callbackURL` and `callbackMethod`.
  - `verify` - the verify function used by the strategy. It must call `done` with
    a user profile as the second argument if the user is valid. This is expected
    to have a `username` property that is used to check against the list of valid
@@ -209,6 +209,8 @@ redirect to following an auth attempt. It must be the URL of your Node-RED edito
 with `/auth/strategy/callback` added to the path. For example, if you access the
 editor at `http://localhost:1880`, you would use `http://localhost:1880/auth/strategy/callback`.
 
+By default, the `callbackURL` will listen for `GET` requests. To use `POST` requests
+instead, set `callbackMethod` to `POST`.
 
 #### Setting a default user
 

index.html

@@ -122,6 +122,8 @@ <h4>In the cloud</h4>
         <div class="content">
             <h3>Who's using Node-RED?</h3>
             <ul id="user-list">
+                <li><a href="https://www.ubos.tech/"><img src="users/ubos.jpg"/></a></li>
+                <li><a href="https://www.bitpool.com/"><img src="users/bitpool.png"/></a></li>
                 <li><a href="https://smartconnect.international/"><img src="users/connect.png"/></a></li>
                 <li><a href="https://www.umh.app/"><img src="users/united-manufacturing-hub.png"/></a></li>
                 <li><a href="https://www.simocowirelesssolutions.com/products/velocity/"/><img src="users/simoco.jpg"/></a></li>