Closed lcnvdl closed 1 year ago
Woww, that was a tough issue to find. I can imagine how frustrating that must have been.
Foal v2 officially only supports v10, 12 and 14 of Node and Foal v3 supports v16 et v18 (see version notes here). All our CLI tests are run against these versions and the framework does not provide support for other ones.
I would recommend to only use versions officially supported to avoid having this kind of issues. Also, odd-numbered versions of Node are not considered stable and contain bugs. It is usually recommended to only go with even versions.
Thank you very much! I didn't remember that FoalTS was targeting specific Node versions. I'll keep that in mind.
Hello FoalTS friends!. I was up all night because my service stopped working after an update, but also I come here with a temporary solution.
I tried endless things, including undoing (minimal) changes I had made to the code. Nothing seemed to fix the problem.
My apps didn't work (only on production environment with docker) because of the next error (always the same, again and again):
I'm deploying my FoalTS microservices using Docker and the image
docker:alpine
.This was my docker file before solving the throuble (node:alpine currently uses NODE_VERSION=19.1.0):
My apps didn't work because of the next error (always the same, again and again):
I tried A LOT of things... The only thing that has been worked for me:
Set an older node version for the container creation (NODE_VERSION=18.12.0):
When downgrading node, everything works normally.
I'm using FoalTS 2.9.0.
My theory is that the problem may come from the fact that the MongoDB library may be out of date. I can't think of anything else at the moment.