These are chat archives for TypeStrong/atom-typescript
atom-typescriptto NPM so it does the same stuff for your
tsconfigon the build server. Will need IOJS. I'll post here once I do that. No timeline right now
typescript.definitionobject in the path
wonder what the build time comparison will be on this monolithic project I have
typings: Microsoft/TypeScript#2338 Will make it a new major release when I do
typingsis not bad. Actually, I think that's the default directory
1.0once this settles. Will also remove
tsd.d.tssince everyone should use
tsd.d.tsfor human convenience.
tsdis how versioning works
declare module "foo"in a given compilation context
/// <reference>as much as I can
@mtraynham / @cmichaelgraham I've made
package.json support more seemless : https://github.com/TypeStrong/atom-typescript#packagejson-support Pushed with V3 as a breaking change.
Expect a V4 if
typescript.definition changes :rose:
@basarat that looks cool !! :) so in the case of aurelia, where one repo may depend on one or more other repos, do you have an idea of how to set that up?
it would be really cool if i could open this folder with atom & atom-typescript and somehow specify the build order for each folder (each of which is an aurelia repo).