Not compatible with TypeScript 4.3+
See original GitHub issueDescribe the bug
Not compatible with TypeScript 4.3+
When using TS4.3, there will be a lot of warnings. But 4.2 is correct.
[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders.
...
I didn’t write any code to modify the properties. Just use @Prop
.
Desktop (please complete the following information):
- OS: MacOS 11.4
- Browser Chrome 91
- Version 9.1.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:6
Top Results From Across the Web
Documentation - TypeScript 4.3
TypeScript now actually does the work to prove whether or not each part of a template string can successfully match. You can now...
Read more >Announcing TypeScript 4.3 - Microsoft Developer Blogs
TypeScript now actually does the work to prove whether or not each part of a template string can successfully match. You can now...
Read more >The Angular Compiler requires TypeScript >=4.2.3 and <4.3.0 ...
1 Answer 1 · npm install typescript@'>==4.2.3 <4.3.0' or npm install typescript@'>==4.2.3 <4.3.0' --save-dev · Go to package.json and change your typescript ......
Read more >Typescript 4.3: remove types compatibility check of getter and ...
Typescript 4.3 : remove types compatibility check of getter and setter from ... type that is not compatible with get accessor type, expecting...
Read more >@typescript-eslint/eslint-plugin - npm
TypeScript plugin for ESLint. ... Start using @typescript-eslint/eslint-plugin in your project by running ... 4.3.0. 56,917. 2 years ago.
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 FreeTop 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
Top GitHub Comments
So the workaround is to add
"useDefineForClassFields": false
to thetsconfig.json
like so:So the result is, that classes are not working in the new ECMA way, but in the old TypeScript way.
Mybe a workaround: https://github.com/microsoft/TypeScript/issues/44449#issuecomment-855257014