-
-
Notifications
You must be signed in to change notification settings - Fork 79
Insights: vuejs/vue-eslint-parser
Overview
-
- 4 Merged pull requests
- 0 Open pull requests
- 1 Closed issue
- 3 New issues
Loading
Could not load contribution data
Please try again later
Loading
4 Pull requests merged by 3 people
-
fix: text token type in V_EXPRESSION_DATA state
#257 merged
Apr 5, 2025 -
Chore: remove codecov workflow
#262 merged
Apr 5, 2025 -
fix: reset vExpressionScriptState when ending mustache
#256 merged
Apr 4, 2025 -
docs: update the location of parserServices
#259 merged
Apr 1, 2025
1 Issue closed by 1 person
-
`<textarea>` content after `}}` causes invalid `vue/no-parsing-error`
#260 closed
Apr 4, 2025
3 Issues opened by 3 people
-
Invalid token type for mustache expression inside `<textarea>`
#261 opened
Apr 4, 2025 -
some kebab-case components name caused eslintno-unused-vars and @typescript-eslint/no-unused-vars
#258 opened
Mar 27, 2025 -
`<script setup>` imports are not hoisted in the presence of a `<script>`
#255 opened
Mar 16, 2025
2 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Using eslint to check TSX in Vue SFC file will throw wrong with "Parsing error: '>' expected"
#247 commented on
Mar 22, 2025 • 0 new comments -
"unsafe member access" errors when using exposed methods from Vue's template `ref`s
#240 commented on
Mar 27, 2025 • 0 new comments