You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the 5.22.9 package. The following error displays upon "npm start" or "twilio serverless start". On my machine I do have nvm installed and don't even have node.js 20.18.1 installed.
WARNING Different Node.js Version Found
│
│ You are currently running Node.js 20.18.1 on this local machine. The production environment for Twilio Serverless currently supports versions 16.,18.x.
│
│ When you deploy to Twilio Serverless, you may encounter differences between local development and production.
│
│ For a more accurate local development experience, please switch your Node.js version.
│ A tool like nvm (https://github.com/creationix/nvm) can help.
When trying to use the Ngrok switch (twilio serverless start --ngrok=xxxxxx --port=3000), the span UNKNOWN error appears and Ngrok will not launch. Manually starting Ngrok works fine.
WARNING Different Node.js Version Found
│
│ You are currently running Node.js 20.18.1 on this local machine. The production environment for Twilio Serverless currently supports versions 16.,18.x.
│
│ When you deploy to Twilio Serverless, you may encounter differences between local development and production.
│
│ For a more accurate local development experience, please switch your Node.js version.
│ A tool like nvm (https://github.com/creationix/nvm) can help.
│ ERROR
│
│ spawn UNKNOWN
The text was updated successfully, but these errors were encountered:
When running the 5.22.9 package. The following error displays upon "npm start" or "twilio serverless start". On my machine I do have nvm installed and don't even have node.js 20.18.1 installed.
When trying to use the Ngrok switch (twilio serverless start --ngrok=xxxxxx --port=3000), the span UNKNOWN error appears and Ngrok will not launch. Manually starting Ngrok works fine.
The text was updated successfully, but these errors were encountered: