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

@tus/server: required node version is incorrect #716

Closed
2 tasks done
mitjap opened this issue Feb 7, 2025 · 0 comments · Fixed by #718
Closed
2 tasks done

@tus/server: required node version is incorrect #716

mitjap opened this issue Feb 7, 2025 · 0 comments · Fixed by #718
Labels

Comments

@mitjap
Copy link
Collaborator

mitjap commented Feb 7, 2025

Initial checklist

  • I understand this is a bug report and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Steps to reproduce

Current implementation of MemoryLock uses AbortSignal.any which was added to version v20.3.0, v18.17.0.

This was added in this commit 42c6267.

In package.json it is defined that this package requires node >= 16 which is not correct.

Expected behavior

@tus/server should require node >= 20.3 or stop using this function.

Actual behavior

Server silently (no error messages on server side) fails on every request and returns status code 500.

TypeError: AbortSignal.any is not a function
    at MemoryLock.lock (.../tus-node-server/packages/server/dist/lockers/MemoryLocker.js:23:41)
    at PostHandler.acquireLock (.../tus-node-server/packages/server/dist/handlers/BaseHandler.js:93:20)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant