Martin

@ricardogobbosouza Using nuxt 2 and nuxt bridge results in the following error ``` FATAL nuxt.hooks.hookOnce is not a function 19:26:38 at setup (node_modules/.pnpm/@[email protected]_47imvc6hy6dc2w6gfpmnntc3hq/node_modules/@nuxtjs/eslint-module/dist/module.mjs:34:16) at ModuleContainer.normalizedModule (node_modules/.pnpm/@[email protected]/node_modules/@nuxt/kit/dist/index.mjs:167:29) at async ModuleContainer.addModule (node_modules/.pnpm/@[email protected]/node_modules/@nuxt/core/dist/core.js:167:20)...

How about just appending a number to the end of the file counting its usage by path since the paths are unique for different images?

@yusufkandemir would it make sense to change the default `module` to a newer value (`NodeNext`) in https://github.com/quasarframework/quasar/blob/9aa98a88cded3362e02c98e47c8c16aeb83ebb13/app-vite/tsconfig-preset.json#L6 Also we should set `"verbatimModuleSyntax": true` and with `NodeNext` we can remove -...

@flowt-au No. Here is the reason: https://en.wikipedia.org/wiki/TypeScript

@Laruxo it's deprecated by the composition api since vue 2.7.

in my e2e tests with selenium / chromedriver I saw the same issue. With nightwatch and gebish. The new value gets appended to the old one.

Any update on this? Edit: For NightwatchJS this seems to be a good approach: https://github.com/nightwatchjs/nightwatch/issues/1132#issuecomment-340257894

> > As for full ESLint v9 support, which is related to the Flat Config milestone, we also need Type Declarations built-into the package so we can use type check...

If someone finds this issue, just do the following: 1. `sudo npm uninstall -g yarn pnpm corepack` - And what else packet is globally installed 2. `sudo pacman -R npm`...

Step 5 enabled the local version of it which was introduced by the global install of corepack via the system package version of pnpm. While pnpm 8.x was still installed...