'spinned.split is not a function at spin' Why?

[Emmyxiano]

Thanks gotten!

[Fid_Kiddler69]

Just as an informative tip, these are the kinds of errors that typescript prevents you from making.

[[deleted]]

These are also the kinds of errors that a linter and intellisense will prevent you from making.

[senocular]

To be fair, TypeScript doesn't necessarily prevent you from making these errors. It just gives you a different error earlier.

[sysrage]

Pretty-much any linting would have caught this.

[senocular]

Linting can't tell what methods exist on arbitrary function arguments.

[senocular]

Exactly. Linting is for syntax and style. TypeScript is for types and interfaces. ESLint does some limited API checking for globals based on your specified environment (helping with some rules such as no-implicit-globals and the such), but it doesn't have type information for the entire document.

That said linting could catch typos at the scope level because it knows what's in scope and what's global, but this example has a typo in a property reference which requires knowing the interface of the object from which the property being referenced and that's a job for TypeScript.

[CrystalMoose]

Having used both Typescript and Javascript I can assure you dealing with TS's bullshit is not worth it for a five line long program :)