at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2723) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:2723) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
14 Aug 14:31:56 - [info] Server now running at http://127.0.0.1:1880/
```
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [14 August 2018 13:44 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/8 "2018-08-14T13:44:55Z")
@cymplecy @ghayne oops. should be `localfilesystem` not `file` in the module field. Have updated the docs.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [14 August 2018 13:53 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/9 "2018-08-14T13:53:03Z")
> [@knolleary](#):
>
> localfilesystem
That works
suggestion to add something in like this to default settings.js
> // By default, the Node-RED UI accepts connections on all IPv4 interfaces.
> // To listen on all IPv6 addresses, set uiHost to "::",
> // The following property can be used to listen on a specific interface. For
> // example, the following would only allow connections from the local machine.
> //uiHost: "127.0.0.1",
>
> // enable persistent storage
> //
> // contextStorage: {
> // default: {
> // module: "localfilesystem"
> // }
> // },
>
> // Retry time in milliseconds for MQTT connections
> mqttReconnectTime: 15000,
---
### Author:  [@shrickus](https://discourse.nodered.org/u/shrickus)
#### Post date: [14 August 2018 14:34 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/10 "2018-08-14T14:34:13Z")
Would also like to see commented-out sample blocks for Projects and Env variables -- assuming they have not already been added (sorry, but I'm not ready to update to 0.19 yet)
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [14 August 2018 14:35 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/11 "2018-08-14T14:35:40Z")
Yup, was on the todo list, but that post-it note fell off my monitor.
---
### Author:  [@real-prometheus](https://discourse.nodered.org/u/real-prometheus)
#### Post date: [14 August 2018 16:54 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/12 "2018-08-14T16:54:14Z")
Hi, what happened to the subflow instance properties? The most promising feature of 0.19 was announced on the roadmap, but I can't find anything about it.
---
### Author:  [@davidcgu](https://discourse.nodered.org/u/davidcgu)
#### Post date: [14 August 2018 17:03 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/13 "2018-08-14T17:03:30Z")
Wow amazing, impatient to test it, just performing a backup of my data and later on full SDcard and will upgrade and remove all my nodes to make persistent data my own and will test.
Thanks u guys
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [14 August 2018 17:08 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/14 "2018-08-14T17:08:02Z")
They are still on the roadmap, but the order of things has shuffled around a bit. Will be doing an update to the roadmap soon to reflect on where we are.
---
### Author:  [@ghayne](https://discourse.nodered.org/u/ghayne)
#### Post date: [14 August 2018 17:16 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/15 "2018-08-14T17:16:20Z")
Working well Nick, nice to have persistence that even survives a re-boot. The right panel is a great improvement. Well done!
---
### Author:  [@real-prometheus](https://discourse.nodered.org/u/real-prometheus)
#### Post date: [14 August 2018 17:46 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/16 "2018-08-14T17:46:40Z")
When do you expect to release the feature? Any rough estimations?
I'm really keen on it, because I have to build complex components and reuse them 20-30 times with different properties. Action flows are doing that job now, but that seems more like a workaround.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [14 August 2018 18:02 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/17 "2018-08-14T18:02:04Z")
> [@real-prometheus](#):
>
> When do you expect to release the feature? Any rough estimations?
As I said, we'll do an update to the roadmap soon to reflect where we are.
We're unlikely to put timescales on particular releases beyond the current one. As an open source project reliant on contributors helping, there are simply too many factors out of my control to put together a schedule of releases for the amount of work the 1.0 roadmap represents.
---
### Author:  [@Andrei](https://discourse.nodered.org/u/Andrei)
#### Post date: [14 August 2018 19:55 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/18 "2018-08-14T19:55:14Z")
Just upgraded in my windows pc with no issues reported during installation. Flows seem all right too.
There is a warning in the manage pallet window. I wonder if this is due to rpi nodes now appearing in windows installations. **Nice improvements** in the design of the sidebar tabs, the wiring of nodes, select node icon, etc..
---
### Author:  [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [14 August 2018 20:29 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/19 "2018-08-14T20:29:57Z")
Just updated to 0.19 & I'm seeing this in the 'context data' window;
I'm presuming it's because of;
```auto
functionGlobalContext: {
fse:require('fs-extra')
```
in my settings file.
But as I'm now saving context to file, will this cause a problem?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [14 August 2018 20:35 UTC](https://discourse.nodered.org/t/node-red-0-19-released/2267/20 "2018-08-14T20:35:09Z")
@Paul-Reed no problem there. But you've highlighted something the docs should spell out a bit more.
The `functionGlobalContext` setting is still used to seed global context, so is still the way to load extra node modules into the Function node.
If you were to do `global.set("fse","123")` that will get written to context storage, and will be the value returned by `global.get("fse")` from then on.
[Next page](https://discourse.nodered.org/t/node-red-0-19-released/2267.md?page=2)