3 ms·
If the library used TypeScript, it wouldn’t have the issue. The point still stands.
by wiseowise 3y ago
If the library used TypeScript, it wouldn’t have the issue.
The point still stands.
- PUSH_AX 3y agoDebatable, and I don’t know how that helps the author. I’m getting huge “silver bullet” sentiment from your replies too.
- wiseowise 3y ago> > obvious problem that was solved decades ago by static typing > getting huge “silver bullet” sentiment from your replies ???
- PUSH_AX 3y agoI didn’t write the first quote, but a comparison to an opinionated strongly typed language where types are a first class citizen, and a typing sandbox with nonsense constructs enabled by antipatterns such as unions (‘string|number’ anyone?)… these are not the same things.
- wiseowise 3y agoWhat makes unions antipattern in your view and why TS is a “sandbox with nonsense constructs”?
- deleted 3y ago[deleted]
- fendy3002 3y agoWhat I get on the issue is that library a using library b which is different version. In this case yes it will solve the issue during tsc or build, only if skipLibCheck flag is turned off.