DanRosenwasser

None taken! It's totally a valid question.

If you're a library author, then our feeling is you want to use `--save` because that saves your consumers the need to install the declaration files themselves.

If you're writing a project that won't be consumed by anyone as a library (e.g. command line tool), it makes sense to make that devDependency.

To clarify what Ryan's getting at, the TypeScript community has started moving to Typings, but there were still issues and pain points that we needed to address to avoid common problems.

While we did write tutorials using Typings, that content will change to use npm by our next release. Our guides are pragmatic, and are meant to get you working with TypeScript today. Making users use nightly releases would've been a major pain.

Hey rhymohr, I think I see what you mean. If you're already using something like Babel & Webpack, it should just be a matter of using a TypeScript loader like ts-loader[1] or awesome-typescript-loader[2]. TypeScript should just fit into that build step.

Let me know how that ends up working out!

[1]: https://github.com/TypeStrong/ts-loader [2]: https://github.com/s-panferov/awesome-typescript-loader

Actually TypeScript powers a JS editing experience codenamed "Salsa" that uses JSDoc comments for types. You can try it out in VS Code where it should currently be enabled.

Give that a shot if you're looking into that sort of workflow.

We also have an official doc on getting started with TypeScript, React, and Webpack if anyone's interested: https://www.typescriptlang.org/docs/handbook/react-&-webpack...

Hey, I work on the TypeScript team. I hope you'll reconsider, and maybe you can fill me in on the issues you ran into.

Your .js files should typically be relative to each other, so unless you're using absolute paths (which you usually shouldn't!), this hasn't been a problem for other users. Is there something that I'm missing?

Hi, dev on TypeScript here. I would not just say that TypeScript "can work" with React, but that it is really very good, especially in terms of JSX tooling. Give it a try some time!

I also wouldn't say TypeScript strives to focus on OO features - we try to be a type system that works well for JavaScript programming as it exists, while paving the way for the future. We don't even use classes in the compiler!

Also like you mentioned, we try hard to work well with many other frameworks and I think that will show. Angular 2, Dojo, Ionic, RxJS, and others are even written in TypeScript and provide a pretty great experience.

I believe the issue is that the code gets parsed as a function expression that is being indexed by a series of strings in comma expressions. This happens instead of automatic semicolon insertion jumping in and then giving you the "expected" code.

As a brief aside, TypeScript could help catch this sort of thing with its `--noImplicitAny` flag turned on.

For a more complete list of features, check out our What's New in TypeScript page:

https://github.com/Microsoft/TypeScript/wiki/What's-new-in-T...

Hi, member of the TypeScript team here. A big reason for the file size increase seems to be the inclusion of an AMD module loader and AMD prologues themselves.

By targeting CommonJS and using Browserify, you see a nice decrease. I've sent out a pull request since finding this.

https://github.com/samccone/The-cost-of-transpiling-es2015-i...

Also check out our "What's New in TypeScript" page[1] for a little more detail.

[1] https://github.com/Microsoft/TypeScript/wiki/What's-new-in-T...

C# is currently supported, with refactoring/navigation support.

See

- https://code.visualstudio.com/docs/languages/overview

- https://code.visualstudio.com/docs/languages/csharp

Hey, TypeScript dev here, what can we do to make your life easier? Y'know, apart from a million bucks.

What kinds of gaps of knowledge do you feel there are in using the two together?

At the very least, true multithreading and compatibility with .NET libraries. It's a great language with its own merits, and worth learning.