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?

Thanks, looks good to me now 🙂

Pull Request Overview

This PR updates thevue/no-import-compiler-macros rule to provide a clearer error message when compiler macros are imported outside of<script setup> blocks. Instead of saying macros "don't need to be imported" (which could be confusing when not in<script setup>), the new message clarifies that these macros "can only be used inside<script setup>".

Key changes:

• Added a new error messageonlyValidInScriptSetup for contexts outside<script setup>
• Updated the rule logic to useutils.isScriptSetup() to determine which message to display
• Added test coverage for non-<script setup> scenarios (regular<script> blocks and TypeScript files)

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

💡Add Copilot custom instructions for smarter, more guided reviews.Learn how to get started.