question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No response returned from render handler [upgraded from RC.12 to 13]

See original GitHub issue

Environment

  • Operating System: Windows_NT
  • Node Version: v18.7.0
  • Nuxt Version: 3.0.0-rc.13
  • Nitro Version: 0.6.1
  • Package Manager: yarn@1.22.19
  • Builder: vite
  • User Config: modules, build, buildModules, vite
  • Runtime Modules: @vueuse/nuxt@9.4.0
  • Build Modules: @vueuse/nuxt@9.4.0

Reproduction

I will edit this section with a template asap

Describe the bug

Just upgraded from RC.12 to RC.13, nothing changed in my repo. Was perfectly working with RC.12, but now I’m getting this white text with a grey background :

No response returned from render handler: /__nuxt_error?url=/&statusCode=500&statusMessage=Vite+Error&message=[vite-node]+[ERR_INVALID_URL_SCHEME]+/node_modules/ufo/dist/index.mjs&stack=%3Cpre%3E%3Cspan+class=%22stack+internal%22%3Eat+/node_modules/ufo/dist/index.mjs%3C/span%3E%3C/pre%3E&data

Additional context

Package.json

{ “private”: true, “scripts”: { “build”: “nuxt build”, “dev”: “nuxt dev”, “generate”: “nuxt generate”, “preview”: “nuxt preview” }, “dependencies”: { “@theatre/core”: “^0.5.0”, “@theatre/studio”: “^0.5.0”, “@vueuse/nuxt”: “^9.3.1”, “glslify”: “^7.1.1”, “gsap”: “^3.11.3”, “howler”: “latest”, “mitt”: “^3.0.0”, “nuxi”: “^3.0.0-rc.13”, “postprocessing”: “^6.29.0”, “three”: “latest”, “tweakpane”: “latest”, “vite-plugin-glsl”: “^0.5.2” }, “devDependencies”: { “@tweakpane/core”: “latest”, “@types/three”: “latest”, “sass”: “^1.49.8” } }

Logs

Nuxi 3.0.0-rc.13                                                                                                                                  20:17:52
Nuxt 3.0.0-rc.13 with Nitro 0.6.1                                                                                                                 20:17:52
                                                                                                                                                  20:17:53
  > Local:    http://localhost:3000/ 

i Vite client warmed up in 3591ms                                                                                                                 20:17:59
√ Nitro built in 698 ms                                                                                                                     nitro 20:18:00
(node:1512) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:16
  • Comments:47 (7 by maintainers)

github_iconTop GitHub Comments

11reactions
Pamavoccommented, Nov 7, 2022

Hi everyone, thanks for your answers.

The bug seems to be related to the path my project was in.

  1. I moved folder from D:\Gobelins\Année-4 to C:\Users\me\Desktop
  2. I removed node_modules folder and yarn.lock file
  3. I ran again yarn install
  4. I ran npx nuxi@latest upgrade --force

These steps fixed the bug for me. I suspect a problem with the part "Année-4". Maybe check the path where your project is located and see if there are any special characters / spaces.

5reactions
phenomenal-hardycommented, Nov 7, 2022

I had the same problem after upgrading from rc12 to rc13, the problem was fixed after I removed the spaces from my project name. If this didn’t work for you there could be spaces in a parent folder of your project.

Thank you very much, got it working, i had a space in a parent folder

this was my project path ( space in “software development” ) C:\Users\pheno\Documents\Software Development\Proyectos\ferreteria-nuxt-app

created a new project folder in desktop and got it working right away

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Mock Service Worker returns empty
The problem is that you're not awaiting for the value but the element, and the element is there when the component is mounted...
Read more >
Error Render when updating to RR 8.3.00
Hi. I have taken a look at the Katana files and the last change was in RR version v8.2.30. There was no change...
Read more >
EventEmitter
Use in components with the @Output directive to emit custom events synchronously or asynchronously, and register handlers for those events by subscribing to ......
Read more >
HTTP Status Codes List | HTTP Error Codes Explained
Status code 102 is an interim response code, telling the client that the server has accepted the full request, but has not completed...
Read more >
React 18 - New Toys, New Footguns, & New Possibilities.
js 13. React Server Components (RSCs) are literally just components that render only on the server, not the client. What are the implications...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found