Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MeiliSearchRequestError when use node js 16.16 #1802

Closed
chu-bin opened this issue Dec 19, 2024 · 3 comments
Closed

MeiliSearchRequestError when use node js 16.16 #1802

chu-bin opened this issue Dec 19, 2024 · 3 comments
Labels
needs investigation Needs to take time to understand the issue.

Comments

@chu-bin
Copy link

chu-bin commented Dec 19, 2024

Description
When meilishechjs is updated to 0.43 and later versions, requests sent to meilishechjs using nodejs 16.16.0 will throw exceptions

Version 0.42 and below do not have this issue

Expected behavior
no error

Current behavior
throw Error

Screenshots or Logs
image

Environment (please complete the following information):
Node v16.16
meiliseach.js >= 0.43
meilseach 1.11.3

@flevi29
Copy link
Collaborator

flevi29 commented Dec 19, 2024

Can't tell what's the full problem from the error, but the documentation about the supported node versions is wrong. Sorry about that.
We're only supporting and testing Node.js 18 and above, the others are EOL.

@curquiza Should we update the docs ASAP?

@flevi29
Copy link
Collaborator

flevi29 commented Dec 19, 2024

Although for @irevoire it worked somehow, so maybe the problem is elsewhere. #1788

@flevi29 flevi29 added the needs investigation Needs to take time to understand the issue. label Dec 19, 2024
@Strift
Copy link
Collaborator

Strift commented Dec 19, 2024

Hi @chu-bin, thanks for opening an issue.

Since both Node 14 and 16 are not supported anymore, I would recommend upgrading your application dependencies if possible. For the same reason, I don't think meilisearch should support these.

This is more of a documentation issue at this point, as @flevi29 pointed out. I opened #1804 to track this.

@Strift Strift closed this as completed Dec 19, 2024
@Strift Strift reopened this Dec 19, 2024
@Strift Strift closed this as not planned Won't fix, can't repro, duplicate, stale Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs investigation Needs to take time to understand the issue.
Projects
None yet
Development

No branches or pull requests

3 participants