Nuxt upgrade from 3.17.5 to 3.17.6 causing 500 "Unable to find global scope" with plugins
Dear Nuxt-Team,
having issues with the latest upgrade and am a bit lost on what could be causing this - i could not find anything in the release notes that would indicate something should break here
Defining a plugin that imports a SwaggerClient (package swagger-client https://www.npmjs.com/package/swagger-client) instance (i don't even have to use it) caused the error "Unable to find global scope. Are you sure this is running in the browser?" so obviously a SSR problem - however until the patch upgrade there were no such issues and nothing has changed with the package
also since this is a project we are currently trying to port from Nuxt 2 we are also still using axios (importing it in a plugin) which also caused problems (but im guessing same root cause - SSR - "FormData undefined")
Please find a minimal reproduction (with swagger-client) here: https://stackblitz.com/edit/github-vavuufks?file=package.json
You will find that if Nuxt is downgraded to 3.17.5 the error disappears.
Any help would be appreciated - thanks!
(wondering if this qualifies as a proper issue but wanted to try here first)
StackBlitz
Nuxt - Starter - StackBlitz
Create a new Nuxt project, module, layer or start from a theme with our collection of starters.
2 Replies
Hi @sa_ra33. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources provided do not contain explicit information about the "Unable to find global scope" error or breaking changes related to plugin imports (such as with
swagger-client or axios) between Nuxt 3.17.5 and 3.17.6. The release notes for 3.17.6 focus on performance improvements, bug fixes, and documentation updates, but do not mention changes that would directly affect global scope handling or SSR compatibility for plugins importing browser-only packages Nuxt 3.17.6 release notes.
Given that downgrading to 3.17.5 resolves the issue, it is possible that an internal change in Nuxt's SSR or plugin handling introduced a regression, but this is not documented in the available sources. If you believe this is a bug, the Nuxt documentation recommends creating a minimal reproduction (which you have done) and reporting it as an issue on the Nuxt GitHub repository, especially if you cannot find an existing issue that matches your problem Reporting Bugs.
If you need further assistance, I recommend opening a GitHub issue with your reproduction link and a detailed description, as this will help the Nuxt team investigate and address the problem.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@735058569400942652> Kapa.ai is still learning and improving, please let me know how I did by reacting below.