Error: Objects are not valid as a React child...
Hello, As of version 3.3.0, we've been having issues with making transcripts and are getting the following error;
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead.
at retryNode (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:6073:17)
at renderNodeDestructive (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:5941:11)
at finishFunctionComponent (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:4841:13)
at renderElement (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:5639:15)
at retryNode (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:5991:31)
at renderNodeDestructive (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:5941:11)
at retryNode (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:6058:15)
at performWork (/root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:6835:17)
at /root/BOT/node_modules/discord-html-transcripts/node_modules/react-dom/cjs/react-dom-server.node.development.js:4473:22
at node:internal/process/task_queues:151:7
When looking thru the changelogs I found #167 which looks like it has to do with React, which is also mentioned in the stacktrace. After downgrading back to 3.2.0 the issues were no longer present.
I have the same issue.
Its deprecated, there is a notice to downgrade to v3.2.0 due to error or something..
Same, hopefully ItzDerock will fix this soon
Eu alugo aplicações, e alguns bots funcionam perfeitamente na versão 3.2.0, enquanto outros não, mesmo sendo baseados exatamente no mesmo sistema. Esse erro tem acontecido com frequência.
@ItzDerock Fix, please
Switch to 3.2.0 have solved that issue for myself: https://github.com/ihrz/ihrz/commit/2da76f9e2bb40582d33d4df1332cd2eebf4b417b