- #110
- #109
- #108
- #107
Is TypeScript a Linter? How to View TS?
By definition, the term Linter usually refers to a tool for static code analysis that checks for specific writing styles. For example, ESLint is the most widely used Linter in the JS ecosystem, helping you check for anti-patterns or dead and outdated code, among other things.
When it comes to TypeScript, it is often imagined as a separate language that requires learning. This idea previously caused me a lot of doubts before adopting or learning it.
TypeScript’s non-invasive design allows it to coexist with JS. As a superset of JS, explaining TS from a Linter’s perspective becomes much easier, as TS is essentially JS but with type checks.
It can be easily adopted and just as easily removed. Writing TS is equivalent to writing JS, but it requires you to have an understanding of types and commit to maintenance. It is essential for medium to large projects.
- #106
- #105
- #104
- #103
- #102
- #101
- #100
- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1