-
-
Notifications
You must be signed in to change notification settings - Fork 795
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
[bug] Pending requests when using Node 16.x #1229
Comments
I had the same issue however it seems that the requests are not getting through to the application. Env serverless -v
Framework Core: 2.43.1
Plugin: 5.1.3
SDK: 4.2.2
Components: 3.10.0
I am using Note: They did not even hit the serverless application, when I removed these routes/endpoints, it should return a 404, (This happens when removing the Hopefully adds some additional information, but like @ApacheEx mentioned, downgrading works: nvm install --lts && nvm use --lts # v14.17.0 at time of comment |
Same error with Node 16.6 :( |
alguém com alguma solução ? aqui também as rotas param de responder se deixar no node 16 |
Same error with node 16.13, I have a GraphQL api and can't even do request on the graphql playground |
I still had the same error with node 16.13.1 - updating to the latest version of sls offline solved the issue. Thank you. |
@darbio which version of sls offline solved the problem? I have the problem too with v6.9.0 |
From my package.json:
|
@darbio I updated and now its working fine! thanks! |
Bug Report
Current Behavior
When I make some XHR requests from my UI application to serverless-offline application. It always shows them with the pending status in the network tab:
from another side, it's started (
serverless offline start
) without any errors.Sample Code
Expected behavior/code
Environment
serverless
version: 2.41.1serverless-offline
version: 7.0.0node.js
version: 16.1.0OS
: macOS 11.3.1 (apple silicon)Possible Solution
downgrading Node to 15.9 or 14.x fixes the issue.
The text was updated successfully, but these errors were encountered: