4 ms·
I'm not bothered by silly things like tone or harsh language, especially for such amazing news. I've actually written my fair share during the summer and I neve
by seivan 11y ago
I'm not bothered by silly things like tone or harsh language, especially for such amazing news. I've actually written my fair share during the summer and I never knew about this.
Thank you! How well would this work with an editor and typescript plugins? Say the amazing typescript-atom, I would guess the editor would crap its pants, no?
- carussell 11y agoWhy not use VSCode instead of Atom? It's (relatively) performant, it has first class support for TypeScript, and if you ever want to hack on it, it's free/open source software (MIT) and written in TypeScript itself.
- DCoder 11y agoA better way would be to do like Arnavion said, for really global libraries you should create a .d.ts file and put this line in it: declare var somelib: any; Done. Now the compiler and everything else will know that there's a global variable called `somelib` that does not have a specific type, and no matter how you use that variable, it's ok, you know what you're doing.
- nothrabannosir 11y agoNo problem. As others mentioned; declare var is the way to go (my TS is getting rusty, apparently :) ). Editors have no problem with it. They will simply see it as an "any" var. Completely compatible. I wrote quite a bit of TS and this was how I used most obscure libraries. I can't be arsed to keep those stupid .d.ts files up to date and I trust the API docs. It's my own code I wanted to vet. Works like a charm. Judicious use of declare var any, and ignoring compiler errors, is what really makes TS reality-compatible.