vue-eslint-parser

Before You File a Bug Report Please Confirm You Have Done The Following... [x] I'm using eslint-plugin-vue. [x] I'm sure the problem is a parser problem. (If you are not sure, search for the issue in eslint-plugin-vue repo and open the issue in eslint-plugin-vue repo if there is no solution. [x] I have tried restarting my IDE and the issue persists. [x] I have updated to the latest version of the packages. What version of ESLint are you using? 8.57 What version of and are you using? vue-eslint-parser@10.1.1 eslint-plugin-vue@10.0.0 What did you do? Configuration What did you expect to happen? The parser should generate an AST similarly to how Vue itself transpiles the code, with the import statements of `ImportDeclarationImportDeclarationExpressionStatementExpressionStatementImportDeclarationExpressionStatementImportDeclarationExpressionStatementimport-x/firstgetScriptSetupCodeBlocksimportCodeBlocksscriptElementgetScriptSetupModuleCodeBlocksCodeBlocksImportDeclarationCodeBlocks`.

Hi, I'm trying to upgrade to from , and I've noticed a change in the API that is breaking things for us. I'm importing and using like this: But in , is exported as a type, not a value, so I get a typing error. I didn't see anything related to this in the changelog, so I'm wondering if it's intentional or not. If it is, what's the proper way to import ? Thank you

Currently the child scopes of the created block scope for `moduleScope.childScopesdefine-model06-with-ts`) fail without changing the code, so I did not additional fixtures. No additional fixture tests fail when applying the fix, so this behavior looks like an oversight. I will add test cases if the new behavior is accepted. Fixes #228.