Deprecation warnings

General
1

I suddenly started receiving a warning every time I Deploy saying,

“The workspace contains some nodes that are not properly configured:” and referring to a Dashboard stylesheet (ui_template) which has the little red pyramid warning.

I have made no change to this node – it is just a CSS collection to generate rounded corners on Dashboard.

I decided to check for upgrades and now have v1.3.5 but no change.

At the command prompt I get 2 x DeprecationWarnings but I have absolutely no idea of what to fix and how, etc.

The Command window listed below gives the following output:

C:\WINDOWS\system32>node-red [ Command prompt]

(node:2220) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\Users{username}\AppData\Roaming\npm\node_modules\node-red\node_modules@node-red\editor-client\package.json' of './lib/index.js'. Please either fix that or report it to the module author

(Use node --trace-deprecation ... to show where the warning was created)

7 Jun 16:13:35 - [info]

Welcome to Node-RED
===================
7 Jun 16:13:35 - [info] Node-RED version: v1.3.5
7 Jun 16:13:35 - [info] Node.js version: v16.1.0
7 Jun 16:13:35 - [info] Windows_NT 10.0.18363 x64 LE
7 Jun 16:13:36 - [info] Loading palette nodes
7 Jun 16:13:37 - [info] Worldmap version 2.15.2
7 Jun 16:13:37 - [info] Dashboard version 2.29.1 started at /ui
7 Jun 16:13:37 - [info] Settings file : C:\Users{username}.node-red\settings.js
7 Jun 16:13:37 - [info] Context store : 'default' [module=memory]
7 Jun 16:13:37 - [info] User directory : \Users{username}.node-red
7 Jun 16:13:37 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Jun 16:13:37 - [info] Flows file : \Users{username}.node-red\flows_WorkStationII.json
(node:2220) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\Users{username}.node-red\node_modules\node-red-dashboard\package.json' of 'none'. Please either fix that or report it to the module author
7 Jun 16:13:37 - [info] Server now running at http://127.0.0.1:1880/
7 Jun 16:13:37 - [warn]

---------------------------------------------------------------------

Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

---------------------------------------------------------------------

7 Jun 16:13:38 - [info] Starting flows
7 Jun 16:13:38 - [info] [worldmap:7970815f.ac5ec] started at /worldmap
7 Jun 16:13:38 - [info] Started flows
7 Jun 16:13:38 - [info] [serialconfig:4dfd20a4.4fdc08] serial port COM7 opened at 9600 baud 8N1

I must say that everything appears to be working on the Dashboard.

Any guidance will be greatly welcome!

2

Have you assigned the ui-control to a valid group and tab and redeployed?

3

Many thanks for your kind assistance.

Template Properties originally said;

Template Type : Added to site section
Name : Dashboard stylesheet

I then changed it to "Widget in group" and selected an operational group and deployed.

Brilliant! Both the red icon and the error warning disappeared upon deployment!

Checking the selected group, the CSS has an effect but not globally. I reverted to the original settings and all still seems to be fine with the CSS applied globally. I'm not sure this is good practice. Perhaps I should set a template for each Group?

I am still getting the start-up deprecation warnings x 2 and really don't know if they are serious or can be disregarded?

4

You can ignore that one, that is because you are using nodejs 16, which causes this warning.

5

Sincere thanks, Colin.

Phew!

6

Apologies to anyone who stumbles across this - I made the error of asking 2 different questions within a single posting without realising they were unrelated. Very fortunately both were kindly answered.

1 Like
7

At the time you had no way of knowing they were unrelated.

2 Likes
8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.