Skip to content
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

Cannot restart nuxt: Maximum call stack size exceeded (sass issue?) #118

Open
cyrdam opened this issue Nov 16, 2023 · 0 comments
Open

Cannot restart nuxt: Maximum call stack size exceeded (sass issue?) #118

cyrdam opened this issue Nov 16, 2023 · 0 comments

Comments

@cyrdam
Copy link

cyrdam commented Nov 16, 2023

Information on system

  • OS: Windows 11
  • package manager: pnpm v8.10.5

Packages

Here are only some packages, but these are the most relevant for the issue:

  • "@nuxtjs/eslint-module": "^4.0.2",
  • "eslint": "^8.40.0",
  • "eslint-plugin-nuxt": "^4.0.0",
  • "eslint-plugin-vue": "^9.12.0",
  • "vite-plugin-eslint": "^1.8.1",
  • "bootstrap": "5.3.0-alpha3",
  • "nuxt": "^3.7.3",
  • "sass": "^1.63.6",
  • "sass-loader": "^13.3.2",

Updating all packages was not fixing the issue, so we left them in that state.

Description

We get following error when starting nuxt with the dev server pnpm run dev:

 ERROR  Cannot start nuxt:  Maximum call stack size exceeded                                                                                                                         09:17:29  

  at formatError (/C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:43993:46)
  at Context.error (/C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:43989:19)
  at Context.buildStart (/C:/dev/project/node_modules/.pnpm/vite-plugin-eslint@1.8.1_eslint@8.40.0_vite@4.4.9/node_modules/vite-plugin-eslint/dist/index.mjs:1:1766)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async Promise.all (index 8)
  at async hookParallel (/C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:43858:9)
  at async Object.buildStart (/C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:44182:13)     
  at async /C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:65230:13
  at async _createServer (/C:/dev/project/node_modules/.pnpm/vite@4.4.9_@types+node@18.16.9_sass@1.63.6/node_modules/vite/dist/node/chunks/dep-df561101.js:65260:9)
  at async buildClient (/C:/dev/project/node_modules/.pnpm/@nuxt+vite-builder@3.7.3_@types+node@18.16.9_eslint@8.40.0_sass@1.63.6_typescript@5.0.4_vue@3.3.4/node_modules/@nuxt/vite-builder/dist/shared/vite-builder.8614ccea.mjs:579:24)

Disabling module-eslint removes this error.
On build this is not happening.

We have the same issue #111 and there are some examples of how to disable repeated messages.
The hints helped to start the dev server with lintOnStart: false. The repeated issues are still coming up, but after the start.

Our issue might be with sass or checking on a style file. We have one SCSS file where we add Bootstrap to it and the rest inside are normal styles with classes. Any other styles are within vue files.

Is there a possibility to trace the files that are checked?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant