Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
0.36.0 breaks Vue SFC's and tests with @vue/test-utils
See original GitHub issueSince the new version (0.36.0), TS will throw errors for things like data- attributes and aria- attributes in Vue SFC files, as well as throw errors when mounting components in tests with @vue/test-utils.
Installing 0.35.2 fixes the issue
0.35.2:
0.36.0:
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Composition API SFC test issue when using Vue 2.7 ... - GitHub
The core of the problem seems to be in @vue/test-utils : When using the compat mode or the 2.7 build, the unit tests...
Read more >Guides | Vue Test Utils
Vue Test Utils (VTU) is a set of utility functions aimed to simplify testing Vue.js components. It provides some methods to mount and...
Read more >Help! My Vue.js Tests are Breaking! - Highland Solutions
It's a large breaking change that removes sync mode from the ... Vue Test Utils is the standard frontend testing framework for Vue.js...
Read more >Write blazing fast Vue unit tests with Tape and Vue Test Utils
I wanted to find out which framework was the fastest for testing Vue SFCs (Single File Components). I added Tape for completeness sake,...
Read more >Testing Vue.js components with Vue Test Utils - LogRocket Blog
Vue Test Utils also allows mocking and stub components to be rendered with shallowMount or individual stubs, but we'll get to that later....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Why would you have to explicitly declare the already valid attributes?
This change makes no sense to me, any
data-*attribute is already according to spec and TS is well aware of it.I don’t understand why this has to be whitelisted. This seems like an unwelcome regression.
Duplicate of #1383