You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The useDefineForClassFields now defaults to true as of Typescript 4.x. I'd be inclined to leave it as true based on their description of it being the most likely standard going forward.
The text was updated successfully, but these errors were encountered:
I was just having a look into this library and came across an issue with recent Typescript (4.3.5)
TLDR - Property injection needs the
declare
keyword. (oruseDefineForClassFields
set to false in tsconfig)I can look at submitting a PR for changing the readme if I get some time and look further into this library.
The issue is described well in the Typescript 3.7 release notes.
The
useDefineForClassFields
now defaults to true as of Typescript 4.x. I'd be inclined to leave it as true based on their description of it being the most likely standard going forward.The text was updated successfully, but these errors were encountered: