Error after scaffolding a new project with create-quasar

[cipher001]

Hey everyone, i'm having issue with scaffolding a new project using the recommended command npm init quasar@latest. This should run the package create-quasar@2.1.0 as of the time of writing.

The project set up part is actually working without issue, but after process has been done and I ran quasar dev inside the project root folder I received the following error message:

node:internal/event_target:1118
  process.nextTick(() => { throw err; });
                           ^
TypeError: FlatESLint is not a constructor
    at Object.configureServer (file:///<my_project_root>/node_modules/vite-plugin-checker/dist/checkers/eslint/main.js:68:20)
    at MessagePort.<anonymous> (file:///<my_project_root>/node_modules/vite-plugin-checker/dist/worker.js:61:26)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:843:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)

so i tried to set useFlatConfig (in quasar.config.ts) to false, which gives:

node:internal/event_target:1118
  process.nextTick(() => { throw err; });
                           ^
Error: Invalid Options:
- Unknown options: extensions, ignorePath, reportUnusedDisableDirectives, resolvePluginsRelativeTo, rulePaths, useEslintrc
- 'extensions' has been removed.
- 'resolvePluginsRelativeTo' has been removed.
- 'ignorePath' has been removed.
- 'rulePaths' has been removed. Please define your rules using plugins.
- 'reportUnusedDisableDirectives' has been removed. Please use the 'overrideConfig.linterOptions.reportUnusedDisableDirectives' option instead.
    at processOptions (<my_project_root>/node_modules/eslint/lib/eslint/eslint-helpers.js:979:9)
    at new ESLint (<my_project_root>/node_modules/eslint/lib/eslint/eslint.js:720:28)
    at Object.configureServer (file:///<my_project_root>/node_modules/vite-plugin-checker/dist/checkers/eslint/main.js:77:18)
    at MessagePort.<anonymous> (file:///<my_project_root>/node_modules/vite-plugin-checker/dist/worker.js:61:26)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:843:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28) {
  code: 'ESLINT_INVALID_OPTIONS'
}

and commenting out the eslint object in vitePlugins gives:

VM initialization failed: Current Mac OS X version 13.0 is lower than minimum supported version 14.0
node:events:486
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:87:19)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

I'm not running a VM in my Mac so this is really puzzling to me. I'm running Node.js v24.14.0 with NVM, and my packge.json:

"dependencies": {
    "axios": "^1.2.1",
    "pinia": "^3.0.1",
    "@quasar/extras": "^1.16.4",
    "quasar": "^2.16.0",
    "vue": "^3.5.22",
    "vue-router": "^5.0.3"
  },
  "devDependencies": {
    "@eslint/js": "^10.0.1",
    "eslint": "^10.0.3",
    "eslint-plugin-vue": "^10.8.0",
    "globals": "^17.4.0",
    "vue-tsc": "^3.2.6",
    "@vue/eslint-config-typescript": "^14.7.0",
    "vite-plugin-checker": "^0.12.0",
    "vue-eslint-parser": "^10.4.0",
    "@vue/eslint-config-prettier": "^10.2.0",
    "prettier": "^3.8.1",
    "@types/node": "^22.19.11",
    "@quasar/app-vite": "^2.5.1",
    "autoprefixer": "^10.4.27",
    "typescript": "^5.9.3"
  },
  "engines": {
    "node": "^28 || ^26 || ^24 || ^22.12",
    "npm": ">= 6.13.4",
    "yarn": ">= 1.21.1",
    "pnpm": ">= 10.0.0"
  }

my OS: macOS Ventura 13.7.8 (22H730)

[yusufkandemir]

Update:

It turns out the ESLint-related problem is due to vite-plugin-checker not supporting ESLint v10 yet: fi3ework/vite-plugin-checker#647
Pushed a fix for it in create-quasar. It will be included in the next release. You can revert to v9 or disable vite-plugin-checker until vite-plugin-checker supports it.

The original answer below only answers the other aspect, which is less common for people to have.

---

Hi there. The underlying issue is very highly likely to come from sass-embedded. I did some research about this. Unfortunately, there is no clear changelog or visible changes anywhere. But I used an LLM to run various commands to verify the actual built dart-sass binaries.

1. Check the bundled Dart VM version in each release:

# sass-embedded 1.97.3 (last working version)
cd /tmp && npm pack sass-embedded-darwin-arm64@1.97.3 && mkdir -p se97 && tar xzf sass-embedded-darwin-arm64-1.97.3.tgz -C se97 && se97/package/dart-sass/src/dart --version

# Dart SDK version: 3.10.7 (stable) (Tue Dec 23 00:01:57 2025 -0800) on "macos_arm64"

# sass-embedded 1.98.0 (broken version)
cd /tmp && npm pack sass-embedded-darwin-arm64@1.98.0 && mkdir -p se98 && tar xzf sass-embedded-darwin-arm64-1.98.0.tgz -C se98 && se98/package/dart-sass/src/dart --version

# Dart SDK version: 3.11.2 (stable) (Tue Mar 10 01:02:11 2026 -0700) on "macos_arm64"

2. Check the minimum macOS deployment target (minos) in each binary:

# sass-embedded 1.97.3
otool -l /tmp/se97/package/dart-sass/src/dart | grep -A2 'minos'
#     minos 11.0
#       sdk 15.1

# sass-embedded 1.98.0
otool -l /tmp/se98/package/dart-sass/src/dart | grep -A2 'minos'
#     minos 14.0
#       sdk 14.4

minos is the Mach-O(Mach object) minimum OS version — the macOS version below which the binary refuses to run, producing the "VM initialization failed" error.

So, you can either upgrade macOS if possible, or pin down sass-embedded and hope it will keep on working. Here's how you can pin it:

For npm, add to package.json:

{
  "overrides": {
    "sass-embedded": "1.97.3"
  }
}

For pnpm, add to package.json:

{
  "pnpm": {
    "overrides": {
      "sass-embedded": "1.97.3"
    }
  }
}

For yarn, add to package.json:

{
  "resolutions": {
    "sass-embedded": "1.97.3"
  }
}

Then remove node_modules and lockfile and reinstall.

[itsalb3rt]

Thanks! I downgrade to v9

[otabekoff]

The same error. Error's main part is:

...
 » App URL................ http://192.168.93.1:9000/
                           http://192.168.229.1:9000/
                           http://10.30.5.27:9000/
                           http://localhost:9000/
                           http://192.168.144.1:9000/
                           http://172.30.208.1:9000/
 » Dev mode............... spa
 » Pkg quasar............. v2.18.7
 » Pkg @quasar/app-vite... v2.5.2
 » Browser target......... baseline-widely-available

 App • Opening default browser at http://localhost:9000/


node:internal/event_target:1122
  process.nextTick(() => { throw err; });
                           ^
TypeError: FlatESLint is not a constructor
....

[otabekoff]

I managed to fix it by running these commands:

bun pm trust --all

bun remove eslint @eslint/js
bun add -D eslint@8 @eslint/js@8

[cipher001]

I got it to work using yusuf's answer, the VM initialization is indeed comes from sass-embedded, downgrading it works for me.
As for the FlatESLint error, I'm pretty sure it's with the eslint rule, so I just disabled the entire eslint object in quasar.config.ts

[otabekoff]

Oh, really? I am glad that you could figure it out. I also found a way to make it work as I said above.

[yusufkandemir]

I edited my answer yesterday with an update. We rolled back ESLint to v9 as the solution.