Please consider fixing issues detected by repository checker

[ioBroker-Bot]

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter twinkly for common errors and appropiate suggestions to keep this adapter up to date.

This check is based on the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.twinkly

-

ERRORS:

• ❗ [E029] Node.js 18 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
• ❗ [E804] Please process issue [#359] "Compatibility check and testing for node.js 22"

WARNINGS:

• 👀 [W028] Minimum node.js version 18 recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
• 👀 [W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json
• 👀 [W156] js-controller 4.0.24 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.
• 👀 [W529] Plugin "manual-review" missing at .releaseconfig.json. Please add.
• 👀 [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

• 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:

@iobroker-bot recheck
or
@iobroker-bot recreate

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 13 Dec 2024 06:28:12 GMT based on commit 02210f6
ioBroker.repochecker 3.2.2

[ioBroker-Bot]

This issue has been updated by ioBroker Check and Service Bot

The following issues have been fixed
[E955] iob_npm.done not found in .npmignore

👍Thanks for fixing the issues.

[ioBroker-Bot]

This issue has been updated by ioBroker Check and Service Bot

The following issues have been fixed
[W028] Minimum node.js version 18 recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.

👍Thanks for fixing the issues.

The following issues are new and have been added
[E029] Node.js 18 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.

[ioBroker-Bot]

This issue has been updated by ioBroker Check and Service Bot

The following issues are new and have been added
[W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json

[ioBroker-Bot]

This issue has been updated by ioBroker Check and Service Bot

The following issues are new and have been added
[E804] Please process issue [#359] "Compatibility check and testing for node.js 22"