xo-cli --register produces "invalid parameters" errors in xo logs
-
@julien-f xo-cli installation runs fine. Trying to run it fails.
I have rolled it back to 0.14.0 and it works fine. -
@mietek Ok, which version of Node are you using?
-
@julien-f v14.21.3
-
@mietek Please use latest Node LTS as explained in the documentation.
-
@julien-f I have installed node LTS ver and the new xo-cli works fine:
nodejs: -> v16.20.0 (Latest LTS: Gallium) xo-cli: āāā xo-cli@0.17.1
Thanks for help.
-
That's why it's important to read the doc, because it means less interruption and more time for @julien-f to actually work on improving XO
-
Hey @julien-f, I have to get back to the issue as I had to move witn node and xo-cli to other machine and even though I have node: v16.20.0 and xo-cli: v0.17.1
I see those errors again.
Is there any way to have it fixed without upgrading xo-server? [ver: 5.87.0] -
@mietek The
No such built-in module: node:assert/strict
cannot occur with Node 16.20.0.What exact issues do you have?
-
If you are using
xo-server 5.87.0
you are indeed very very outdated. Remember to keep everything up to date onmaster
branch as possible. -
@julien-f Hey, I am back to the original issue now:
"message": "should not contains property ["description"]If there is anything I can do to not have it in logs then great, but if not
@olivierlambert might be right that it's time to finally upgrade the server version. -
@mietek I cannot reproduce the problem with
xo-cli@0.17.1
, either withxo-server@5.87.0
nor withxo-server@5.111.1
.Anyway, old versions are not supported, please upgrade.
If you have a paying subscription and a special need, please open a support ticket.
-
@julien-f OK, server upgrade it is.
Thanks for a prompt reply. Appreciate it.