Flo Edelmann

In #2701, the rule was already improved to only report the `export` keyword for statements that might be relevant for local code, e.g.: ```ts export const foo = 'bar' console.log(foo)...

> It would be ideal if `vue/no-multi-spaces` were able to use the global setting and ignore comments in this case. That is not possible; the rule only knows its own...

This has nothing to do with `projectService`. It's that you tell ESLint to parse Vue files with typescript-eslint's parser. Instead, you have to use eslint-parser-vue, which in turn you can...

~~You need to add `"./**/*.vue"` to the `"include"` option in your `tsconfig.json`.~~ **EDIT:** `"src/**/*.vue"` was already included in the reproduction.

> `"src/**/*.vue"` should already be included. Oh right. I have a pretty similar setup (but still on ESLint v8 with `.eslintrc.js` config format, and without JSX) and it works fine...

So you don't have typed linting with ESLint 8? Could you try whether that works?

SCSS imports are now [deprecated](https://sass-lang.com/blog/import-is-deprecated/), so I'd say `import-notation: url` is fine in the recommended config. It can still be overridden manually with `import-notation: null`.

That is now merged and released (https://github.com/stylelint-scss/stylelint-scss/releases/tag/v6.8.0), so this issue should be unblocked now.

# Export files validity (Output of test script `tests/github/exports-valid.js`.) Test the exported files of selected fixtures against the plugins' export tests. You can run a plugin's export tests by executing:...

# Export files validity (Output of test script `tests/github/exports-valid.js`.) Test the exported files of selected fixtures against the plugins' export tests. You can run a plugin's export tests by executing:...