fix(no-import-compiler-macros): check only in <script setup>

[Sysix]

After reading #2437, I found out that the compiler warnings are only reported at <script setup>:
https://github.com/vuejs/core/blob/c16f8a94c7eda79f51f44b7b3c64c72343df0d38/packages/compiler-sfc/src/compileScript.ts#L321-L355

Changed the rule to only look inside <script setup> and not other files like someMacro.ts.

Copied the logic from

eslint-plugin-vue/lib/rules/valid-define-emits.js

Lines 31 to 46 in 553abe6

	create(context) {
	const scriptSetup = utils.getScriptSetupElement(context)
	if (!scriptSetup) {
	return {}
	}
	/** @type {Set<Expression | SpreadElement>} */
	const emitsDefExpressions = new Set()
	let hasDefaultExport = false
	/** @type {CallExpression[]} */
	const defineEmitsNodes = []
	/** @type {CallExpression | null} */
	let emptyDefineEmits = null
	return utils.compositingVisitors(
	utils.defineScriptSetupVisitor(context, {

[changeset-bot]

🦋 Changeset detected

Latest commit: f1e1ddb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
eslint-plugin-vue	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[FloEdelmann]

It's true that Vue emits the runtime warning only in <script setup>, but I think that is because the compiler macros are only available in <script setup>. So while it would be more correct for the ESLint rule to only report compiler macro imports in <script setup>, it would not really make sense to import them outside <script setup>, too, would it?

[Sysix]

it would not really make sense to import them outside <script setup>, too, would it?

That was my guess too. But they can be wrongly imported by the user.
Do not know what the bundler/vue-compiler will do. Maybe a new ESLint rule like no-compilier-macros-outside-script-setup?

Updated the tests 👍

[FloEdelmann]

But they can be wrongly imported by the user.

But the vue/no-import-compiler-macros already warns about that case, while this PR removes exactly this warning. So I think the current behavior is better.

Do you agree? If so, feel free to update the PR to only improve test coverage for the non-<script setup> case. Otherwise, I'm open for discussion 🙂

[Sysix]

I would prefer an own error/diagnostic message for using compiler macros outside Vue files.
Do you think it is okay to include it in this rule?
Something like

'{{name}} is a compiler macro and is only valid inside `<script>`with "setup".