Im using an Boosted replit to run NUXT 3.0. I
m getting the message on my webview when I try to access it.
Do I need to buy cycles? My replit resources don’t seem to be used as much.
Appreciate your help.
Im using an Boosted replit to run NUXT 3.0. I
m getting the message on my webview when I try to access it.
Do I need to buy cycles? My replit resources don’t seem to be used as much.
Appreciate your help.
In the meantime also bought cycles and did more upgrades, without success.
I Changed my replit configuration file to be able to boot it using the run button, then I got to run it without the webview.
This seems to be a Nuxt.js error, not anything wrong with the Repl in particular. What happens if you delete the build folder and rebuild?
I removed .nuxt, node_modules and package-lock and started with a fresh install. No success.
Message seems to came from replit/devtools
The injected URL is https://94f2b423-7c65-4ff8-890a-cd4dd6e5ecb2.id.repl.co/__replco/devtools_wrapper.html
The Error seems to be coming from what is not part of Vue or Nuxt.
@dragonhunter1 @ReplitIronclad
I tried to create a public repo with nuxt 3 ssr:true to test without any of my custom setup and still show upgrade required.
https://replit.com/@LucasSchirm/Nuxt-3-Basic-Setup
Also add this, since other people seems to be going throught the same issue.
What happens when you update to node.js v18?
Is actually already running on v18.12.1! The github post is not mine, is another person with the same issue.
Did you find anything else by any chance?
I’m sorry, I’m very unfamilliar with Nuxt.js. I’ll pass it along to someone who’s familliar with the stack.
cc @TheDrone7
I got a response, there is an issue with ports. Make sure you’re exposing the host 0.0.0.0
with your application.
It’s an issue with the ports, nuxt runs 2 servers 1 for the actual site itself and one that actively builds the site for hmr and stuff. Replit often exposes the wrong port cuz the one that is needed to build the project starts first and displays “Upgrade required” and then even when the other server, which is the actual site starts, does not get exposed. (edited)
You can configure port exposing in Replit as shown here: https://docs.replit.com/programming-ide/configuring-repl#ports
~/Nuxt-3-Basic-Setup$ netstat -tulpn | grep node
tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 3563/node
tcp6 0 0 :::24678 :::* LISTEN 3563/node
Try setting the externalPort
to 24678 and the localPort
to 3000.
Thank you will try it later today.