<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>TypeScript</title><link>http://typescript.codeplex.com/project/feeds/rss</link><description>TypeScript is a language for application-scale JavaScript development. TypeScript is a typed superset of JavaScript that compiles to plain JavaScript.</description><item><title>New Post: Debugging TypeScript in Visual Studio (assets served with Cassette)</title><link>http://typescript.codeplex.com/discussions/444245</link><description>&lt;div style="line-height: normal;"&gt;The debugging support in TypeScript uses the source map format that a number of JS tools support, including browsers like Chrome as well.  The .map file maps from the output .js file back to the original .ts file.  If Visual Studio can't access the .map file, it won't be able to successfully debug directly on your original TS files.&lt;br /&gt;
&lt;br /&gt;
By default, a new TypeScript HTML5 project will create a .map file as part of a debug build.  If you're using your own project not based on that template, you'll need to enable source map output yourself using the &amp;quot;--sourcemap&amp;quot; commandline option.&lt;br /&gt;
&lt;br /&gt;
I'm not familiar Cassette, though as you describe it may be introducing a layer of abstraction that's not compatible with the VS plugin.  It may be worth trying a simpler setup first to see if you can have success with that.&lt;br /&gt;
&lt;/div&gt;</description><author>jonturner</author><pubDate>Mon, 20 May 2013 16:01:22 GMT</pubDate><guid isPermaLink="false">New Post: Debugging TypeScript in Visual Studio (assets served with Cassette) 20130520040122P</guid></item><item><title>New Post: Debugging TypeScript in Visual Studio (assets served with Cassette)</title><link>http://typescript.codeplex.com/discussions/444245</link><description>&lt;div style="line-height: normal;"&gt;The debugging support in TypeScript uses the source map format that a number of JS tools support, including browsers like Chrome as well.  The .map file maps from the output .js file back to the original .ts file.  If Visual Studio can't access the .map file, it won't be able to successfully debug directly on your original TS files.&lt;br /&gt;
&lt;br /&gt;
By default, a new TypeScript HTML5 project will create a .map file as part of a debug build.  If you're using your own project not based on that template, you'll need to enable source map output yourself using the &amp;quot;--sourcemap&amp;quot; commandline option.&lt;br /&gt;
&lt;br /&gt;
I'm not familiar Cassette, though as you describe it may be introducing a layer of abstraction that's not compatible with the VS plugin.  It may be worth trying a simpler setup first to see if you can have success with that.&lt;br /&gt;
&lt;/div&gt;</description><author>jonturner</author><pubDate>Mon, 20 May 2013 16:01:22 GMT</pubDate><guid isPermaLink="false">New Post: Debugging TypeScript in Visual Studio (assets served with Cassette) 20130520040122P</guid></item><item><title>New Post: Long compilation time in 0.9?</title><link>http://typescript.codeplex.com/discussions/442828</link><description>&lt;div style="line-height: normal;"&gt;Like you say, the Jakefile outputs the tsc.js, which you can run with any ES3-compatible JS engine.  When we ship the .exe, we build it in-house and ship with a Microsoft JS engine.  You could think of the .exe as the same as the tsc.js, except we pick the engine for you.&lt;br /&gt;
&lt;/div&gt;</description><author>jonturner</author><pubDate>Mon, 20 May 2013 15:56:49 GMT</pubDate><guid isPermaLink="false">New Post: Long compilation time in 0.9? 20130520035649P</guid></item><item><title>New Post: Long compilation time in 0.9?</title><link>http://typescript.codeplex.com/discussions/442828</link><description>&lt;div style="line-height: normal;"&gt;Like you say, the Jakefile outputs the tsc.js, which you can run with any ES3-compatible JS engine.  When we ship the .exe, we build it in-house and ship with a Microsoft JS engine.  You could think of the .exe as the same as the tsc.js, except we pick the engine for you.&lt;br /&gt;
&lt;/div&gt;</description><author>jonturner</author><pubDate>Mon, 20 May 2013 15:56:49 GMT</pubDate><guid isPermaLink="false">New Post: Long compilation time in 0.9? 20130520035649P</guid></item><item><title>New Comment on "Known breaking changes between 0.8 and 0.9"</title><link>https://typescript.codeplex.com/wikipage?title=Known breaking changes between 0.8 and 0.9&amp;ANCHOR#C27534</link><description>&amp;#64;mihailik&amp;#10;&amp;#10;Thanks, I&amp;#39;m actually aware that you can use lambdas like that, my hope was to get the ability to use functions like that as well.&amp;#10;&amp;#10;Lambdas stored in a var cause a few problems in my opinion&amp;#58; they don&amp;#39;t work for inheritance, they&amp;#39;re mutable so they can be changed, they can have order of initialization problems, and they don&amp;#39;t contain any sort of name property to identify them, which is bad for call stacks, and metaprogramming.&amp;#10;&amp;#10;I really like the use of short functions that return their results immediately.  For me, limiting yourself to a single computational result for a function is a great way to increase the modularity, and composability of your functions.  It gets even better when you can partially apply functions to set up context, and then invoke them later with the rest of the arguments.&amp;#10;&amp;#10;I&amp;#39;ve been using this technique along with the fact that you can extract the name of named functions as a type safe mapping layer between my client and server side code, as well as for handling routing page rendering in the client side. Without the named arrow functions, my code will unfortunately get much longer and more cumbersome.&amp;#10;&amp;#10;I&amp;#39;m sure that these things are probably much more of a concern to me than they are to other people, but I figured I&amp;#39;d mention them anyways &amp;#58;D</description><author>dlshryock</author><pubDate>Mon, 20 May 2013 14:52:34 GMT</pubDate><guid isPermaLink="false">New Comment on "Known breaking changes between 0.8 and 0.9" 20130520025234P</guid></item><item><title>New Post: Real world projects written is TypeScript</title><link>http://typescript.codeplex.com/discussions/430577</link><description>&lt;div style="line-height: normal;"&gt;A Leap Motion library written in TypeScript: &lt;a href="https://github.com/logotype/LeapMotionTS" rel="nofollow"&gt;https://github.com/logotype/LeapMotionTS&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://www.leapmotion.com" rel="nofollow"&gt;www.leapmotion.com&lt;/a&gt;&lt;br /&gt;
&lt;/div&gt;</description><author>logotype</author><pubDate>Mon, 20 May 2013 06:37:50 GMT</pubDate><guid isPermaLink="false">New Post: Real world projects written is TypeScript 20130520063750A</guid></item><item><title>New Post: Real world projects written is TypeScript</title><link>http://typescript.codeplex.com/discussions/430577</link><description>&lt;div style="line-height: normal;"&gt;A Leap Motion library written in TypeScript: &lt;a href="https://github.com/logotype/LeapMotionTS" rel="nofollow"&gt;https://github.com/logotype/LeapMotionTS&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://www.leapmotion.com" rel="nofollow"&gt;www.leapmotion.com&lt;/a&gt;&lt;br /&gt;
&lt;/div&gt;</description><author>logotype</author><pubDate>Mon, 20 May 2013 06:37:50 GMT</pubDate><guid isPermaLink="false">New Post: Real world projects written is TypeScript 20130520063750A</guid></item><item><title>New Post: Single file output does not work with extends</title><link>http://typescript.codeplex.com/discussions/444124</link><description>&lt;div style="line-height: normal;"&gt;Hi&lt;br /&gt;
&lt;br /&gt;
Try to switch the order:&lt;br /&gt;
$ tsc --out out.js Child.ts Parent.ts  &amp;amp;&amp;amp; node out&lt;br /&gt;
&lt;br /&gt;
I've noticed the same error in my projects, and the file order does matter when compiling. It shouldn't though? Hope this gets fixed.&lt;br /&gt;
&lt;/div&gt;</description><author>logotype</author><pubDate>Mon, 20 May 2013 06:34:07 GMT</pubDate><guid isPermaLink="false">New Post: Single file output does not work with extends 20130520063407A</guid></item><item><title>New Post: Single file output does not work with extends</title><link>http://typescript.codeplex.com/discussions/444124</link><description>&lt;div style="line-height: normal;"&gt;Hi&lt;br /&gt;
&lt;br /&gt;
Try to switch the order:&lt;br /&gt;
$ tsc --out out.js Child.ts Parent.ts  &amp;amp;&amp;amp; node out&lt;br /&gt;
&lt;br /&gt;
I've noticed the same error in my projects, and the file order does matter when compiling. It shouldn't though? Hope this gets fixed.&lt;br /&gt;
&lt;/div&gt;</description><author>logotype</author><pubDate>Mon, 20 May 2013 06:34:07 GMT</pubDate><guid isPermaLink="false">New Post: Single file output does not work with extends 20130520063407A</guid></item><item><title>New Post: Single file output does not work with extends</title><link>http://typescript.codeplex.com/discussions/444124</link><description>&lt;div style="line-height: normal;"&gt;Hi&lt;br /&gt;
&lt;br /&gt;
Try to switch the order:&lt;br /&gt;
$ tsc --out out.js Child.ts Parent.ts  &amp;amp;&amp;amp; node out&lt;br /&gt;
&lt;br /&gt;
I've noticed the same error in my projects, and the file order does matter when compiling. It shouldn't though? Hope this gets fixed.&lt;br /&gt;
&lt;/div&gt;</description><author>logotype</author><pubDate>Mon, 20 May 2013 06:34:07 GMT</pubDate><guid isPermaLink="false">New Post: Single file output does not work with extends 20130520063407A</guid></item><item><title>New Post: Real world projects written is TypeScript</title><link>http://typescript.codeplex.com/discussions/430577</link><description>&lt;div style="line-height: normal;"&gt;Yesterday there was  published new framework &lt;a href="https://github.com/BBGONE/jRIAppTS" rel="nofollow"&gt;https://github.com/BBGONE/jRIAppTS&lt;/a&gt;&lt;br /&gt;
the client part was written in typescript.&lt;br /&gt;
It makes possible to create data centric HTML5 applications in the strongly typed way.&lt;br /&gt;
The data binding style is close to Microsoft's Silverlight and WPF style.&lt;br /&gt;
The data service can generate strongly type DbSets, Entities, DbContext in typescript.&lt;br /&gt;
You can have lookups, autocompletes, dataform, datagrid out of the box.&lt;br /&gt;
Or you can remove those modules from the framework and use this curtailed version like  you use knockout.js.&lt;br /&gt;
&lt;/div&gt;</description><author>BBGONE</author><pubDate>Mon, 20 May 2013 06:32:08 GMT</pubDate><guid isPermaLink="false">New Post: Real world projects written is TypeScript 20130520063208A</guid></item><item><title>New Post: Real world projects written is TypeScript</title><link>http://typescript.codeplex.com/discussions/430577</link><description>&lt;div style="line-height: normal;"&gt;Yesterday there was  published new framework &lt;a href="https://github.com/BBGONE/jRIAppTS" rel="nofollow"&gt;https://github.com/BBGONE/jRIAppTS&lt;/a&gt;&lt;br /&gt;
the client part was written in typescript.&lt;br /&gt;
It makes possible to create data centric HTML5 applications in the strongly typed way.&lt;br /&gt;
The data binding style is close to Microsoft's Silverlight and WPF style.&lt;br /&gt;
The data service can generate strongly type DbSets, Entities, DbContext in typescript.&lt;br /&gt;
You can have lookups, autocompletes, dataform, datagrid out of the box.&lt;br /&gt;
Or you can remove those modules from the framework and use this curtailed version like  you use knockout.js.&lt;br /&gt;
&lt;/div&gt;</description><author>BBGONE</author><pubDate>Mon, 20 May 2013 06:32:08 GMT</pubDate><guid isPermaLink="false">New Post: Real world projects written is TypeScript 20130520063208A</guid></item><item><title>New Post: Debugging TypeScript in Visual Studio (assets served with Cassette)</title><link>http://typescript.codeplex.com/discussions/444245</link><description>&lt;div style="line-height: normal;"&gt;Hi All,&lt;br /&gt;
&lt;br /&gt;
Are you aware of any good resources around debugging TypeScript in Visual Studio?&lt;br /&gt;
&lt;br /&gt;
In my situation I'm using Cassette ( &lt;a href="http://getcassette.net/" rel="nofollow"&gt;http://getcassette.net/&lt;/a&gt; ) to serve up my JavaScript to the browser - and maybe that's causing the issue.  The JavaScript I'm serving has been generated by my TypeScript. But for the life of me I've got no joy in getting Visual Studio to allow me to debug the TS when serving&lt;br /&gt;
&lt;br /&gt;
I'm wondering if I need to be serving up the *.js.map files as well?  I've tried it but it just generates errors.  (Fair enough - they're not legitimate script files I guess).  I can also see the following statement being generated which is map related:&lt;br /&gt;
&lt;br /&gt;
//@ sourceMappingURL=Index.js.map&lt;br /&gt;
&lt;br /&gt;
However, I've no clue what this is for.  Any idea of good places to look for info on this?&lt;br /&gt;
&lt;/div&gt;</description><author>johnny_reilly</author><pubDate>Mon, 20 May 2013 05:18:58 GMT</pubDate><guid isPermaLink="false">New Post: Debugging TypeScript in Visual Studio (assets served with Cassette) 20130520051858A</guid></item><item><title>New Post: Debugging TypeScript in Visual Studio (assets served with Cassette)</title><link>http://typescript.codeplex.com/discussions/444245</link><description>&lt;div style="line-height: normal;"&gt;Hi All,&lt;br /&gt;
&lt;br /&gt;
Are you aware of any good resources around debugging TypeScript in Visual Studio?&lt;br /&gt;
&lt;br /&gt;
In my situation I'm using Cassette ( &lt;a href="http://getcassette.net/" rel="nofollow"&gt;http://getcassette.net/&lt;/a&gt; ) to serve up my JavaScript to the browser - and maybe that's causing the issue.  The JavaScript I'm serving has been generated by my TypeScript. But for the life of me I've got no joy in getting Visual Studio to allow me to debug the TS when serving&lt;br /&gt;
&lt;br /&gt;
I'm wondering if I need to be serving up the *.js.map files as well?  I've tried it but it just generates errors.  (Fair enough - they're not legitimate script files I guess).  I can also see the following statement being generated which is map related:&lt;br /&gt;
&lt;br /&gt;
//@ sourceMappingURL=Index.js.map&lt;br /&gt;
&lt;br /&gt;
However, I've no clue what this is for.  Any idea of good places to look for info on this?&lt;br /&gt;
&lt;/div&gt;</description><author>johnny_reilly</author><pubDate>Mon, 20 May 2013 05:18:58 GMT</pubDate><guid isPermaLink="false">New Post: Debugging TypeScript in Visual Studio (assets served with Cassette) 20130520051858A</guid></item><item><title>Edited Unassigned: Copy-paste annoyance in Visual Studio [1036]</title><link>http://typescript.codeplex.com/workitem/1036</link><description>Hi, to reproduce&amp;#58;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;#42; Enter the following bit of text in any TypeScript file in Visual Studio.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#47;Bar&amp;#47;Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo-Bar-Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#43;&amp;#61;Bar&amp;#43;&amp;#61;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;&amp;#42; Copy any single line of text, omitting the comment slash, e.g. copy &amp;#34;Foo&amp;#47;Bar&amp;#47;Baz&amp;#34; into the clipboard.&lt;br /&gt;&lt;br /&gt;&amp;#42; Paste it back into the TypeScript file.&lt;br /&gt;&lt;br /&gt;&amp;#42; The pasted text is rendered with code formatting&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Foo&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Bar&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;Text pasted from the clipboard should not undergo any formatting. &lt;br /&gt;&lt;br /&gt;This is the behaviour in other code files in Visual Studio, such as C&amp;#35;.&lt;br /&gt;</description><author>nabog</author><pubDate>Sun, 19 May 2013 10:12:19 GMT</pubDate><guid isPermaLink="false">Edited Unassigned: Copy-paste annoyance in Visual Studio [1036] 20130519101219A</guid></item><item><title>Reopened Unassigned: Copy-paste annoyance in Visual Studio [1036]</title><link>http://typescript.codeplex.com/workitem/1036</link><description>Hi, to reproduce&amp;#58;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;#42; Enter the following bit of text in any TypeScript file in Visual Studio.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#47;Bar&amp;#47;Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo-Bar-Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#43;&amp;#61;Bar&amp;#43;&amp;#61;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;&amp;#42; Copy any single line of text, omitting the comment slash, e.g. copy &amp;#34;Foo&amp;#47;Bar&amp;#47;Baz&amp;#34; into the clipboard.&lt;br /&gt;&lt;br /&gt;&amp;#42; Paste it back into the TypeScript file.&lt;br /&gt;&lt;br /&gt;&amp;#42; The pasted text is rendered with code formatting&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Foo&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Bar&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;Text pasted from the clipboard should not undergo any formatting. &lt;br /&gt;&lt;br /&gt;This is the behaviour in other code files in Visual Studio, such as C&amp;#35;.&lt;br /&gt;</description><author>nabog</author><pubDate>Sun, 19 May 2013 10:12:13 GMT</pubDate><guid isPermaLink="false">Reopened Unassigned: Copy-paste annoyance in Visual Studio [1036] 20130519101213A</guid></item><item><title>Commented Unassigned: Copy-paste annoyance in Visual Studio [1036]</title><link>http://typescript.codeplex.com/workitem/1036</link><description>Hi, to reproduce&amp;#58;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;#42; Enter the following bit of text in any TypeScript file in Visual Studio.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#47;Bar&amp;#47;Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo-Bar-Baz&lt;br /&gt;        &amp;#47;&amp;#47; Foo&amp;#43;&amp;#61;Bar&amp;#43;&amp;#61;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;&amp;#42; Copy any single line of text, omitting the comment slash, e.g. copy &amp;#34;Foo&amp;#47;Bar&amp;#47;Baz&amp;#34; into the clipboard.&lt;br /&gt;&lt;br /&gt;&amp;#42; Paste it back into the TypeScript file.&lt;br /&gt;&lt;br /&gt;&amp;#42; The pasted text is rendered with code formatting&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Foo&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Bar&amp;#123;space&amp;#125;&amp;#47;&amp;#123;space&amp;#125;Baz&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;Text pasted from the clipboard should not undergo any formatting. &lt;br /&gt;&lt;br /&gt;This is the behaviour in other code files in Visual Studio, such as C&amp;#35;.&lt;br /&gt;Comments: I believe the &amp;#34;Automatically format on paste&amp;#34; behaviour in the TypeScript editor is a bit faulty.&amp;#10;&amp;#10;I already have this checked for C&amp;#35; but the C&amp;#35; edit does not have the behaviour that I described in my original post. I think the C&amp;#35; editor is clever enough to only attempt to format pasted text that was already formatted when it was copied to the clipboard.&amp;#10;&amp;#10;If I uncheck the TypeScript option &amp;#34;Format on paste&amp;#34; then nothing gets formatted on paste, for example copying and pasting a method within a class leads to unformatted code.&amp;#10;&amp;#10;I would like to keep &amp;#34;Format on paste&amp;#34; on, but that shouldn&amp;#39;t attempt to format previously unformatted text pasted from the clipboard.</description><author>nabog</author><pubDate>Sun, 19 May 2013 10:12:10 GMT</pubDate><guid isPermaLink="false">Commented Unassigned: Copy-paste annoyance in Visual Studio [1036] 20130519101210A</guid></item><item><title>Commented Issue: Invalid sourcemap when combining 2 files [1032]</title><link>http://typescript.codeplex.com/workitem/1032</link><description>Created from a comment in this issue&amp;#58; https&amp;#58;&amp;#47;&amp;#47;typescript.codeplex.com&amp;#47;workitem&amp;#47;772 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;TypeScript compiler creates an invalid sourcemap when combining the following 2 files&lt;br /&gt;&lt;br /&gt;&amp;#64;animal.ts&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;module animals &amp;#123;&lt;br /&gt;&lt;br /&gt;  export class Animal &amp;#123;&lt;br /&gt;    private killed&amp;#59;&lt;br /&gt;&lt;br /&gt;    kill&amp;#40;&amp;#41; &amp;#123;&lt;br /&gt;      this.killed &amp;#61; true&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;  &amp;#125;&lt;br /&gt;&lt;br /&gt;&amp;#125;&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&amp;#64;dog.ts&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;module animals &amp;#123;&lt;br /&gt;&lt;br /&gt;  class Dog extends Animal &amp;#123;&lt;br /&gt;    bark&amp;#40;&amp;#41; &amp;#123;&lt;br /&gt;      console.log&amp;#40;&amp;#39;bark&amp;#39;&amp;#41;&lt;br /&gt;    &amp;#125;&lt;br /&gt;  &amp;#125;&lt;br /&gt;&lt;br /&gt;&amp;#125;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&lt;br /&gt;validate using source-map module in node&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;var SourceMapConsumer &amp;#61; require&amp;#40;&amp;#39;source-map&amp;#39;&amp;#41;.SourceMapConsumer&amp;#59;&lt;br /&gt;new SourceMapConsumer&amp;#40;require&amp;#40;&amp;#39;fs&amp;#39;&amp;#41;.readFileSync&amp;#40;&amp;#39;bug.js.map&amp;#39;, &amp;#39;utf8&amp;#39;&amp;#41;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Comments: Please find attached a patch which I believe fixes the issue.</description><author>Naav</author><pubDate>Sat, 18 May 2013 14:28:49 GMT</pubDate><guid isPermaLink="false">Commented Issue: Invalid sourcemap when combining 2 files [1032] 20130518022849P</guid></item><item><title>New Post: Single file output does not work with extends</title><link>http://typescript.codeplex.com/discussions/444124</link><description>&lt;div style="line-height: normal;"&gt;Extends clause does not work when concatenating and emitting output to single file. The generated output seems to have the classes in the wrong order. Varying results can be achieved by changing the order in which files given in the tsc command line.&lt;br /&gt;
&lt;br /&gt;
Parent.ts&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;class Parent {
}&lt;/code&gt;&lt;/pre&gt;

Child.ts&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;class Child extends Parent {
}&lt;/code&gt;&lt;/pre&gt;

For example:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;$ tsc --out out.js Child.ts Parent.ts &amp;amp;&amp;amp; node out

typescript-extends-undefined-bug\out.js:3
    __.prototype = b.prototype;
                    ^
TypeError: Cannot read property 'prototype' of undefined
    at __extends (typescript-extends-undefined-bug\out.js:3:21)
    at typescript-extends-undefined-bug\out.js:7:5
    at Object.&amp;lt;anonymous&amp;gt; (typescript-extends-undefined-bug\out.js:13:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:901:3&lt;/code&gt;&lt;/pre&gt;

And when switching the argument file order, no error:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;$ tsc --out out.js Parent.ts Child.ts &amp;amp;&amp;amp; node out&lt;/code&gt;&lt;/pre&gt;

Typescript version 0.8.3.0. Node.js version v0.10.1.&lt;br /&gt;
&lt;/div&gt;</description><author>PSP2</author><pubDate>Sat, 18 May 2013 09:49:25 GMT</pubDate><guid isPermaLink="false">New Post: Single file output does not work with extends 20130518094925A</guid></item><item><title>New Post: Single file output does not work with extends</title><link>http://typescript.codeplex.com/discussions/444124</link><description>&lt;div style="line-height: normal;"&gt;Extends clause does not work when concatenating and emitting output to single file. The generated output seems to have the classes in the wrong order. Varying results can be achieved by changing the order in which files given in the tsc command line.&lt;br /&gt;
&lt;br /&gt;
Parent.ts&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;class Parent {
}&lt;/code&gt;&lt;/pre&gt;

Child.ts&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;class Child extends Parent {
}&lt;/code&gt;&lt;/pre&gt;

For example:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;$ tsc --out out.js Child.ts Parent.ts &amp;amp;&amp;amp; node out

typescript-extends-undefined-bug\out.js:3
    __.prototype = b.prototype;
                    ^
TypeError: Cannot read property 'prototype' of undefined
    at __extends (typescript-extends-undefined-bug\out.js:3:21)
    at typescript-extends-undefined-bug\out.js:7:5
    at Object.&amp;lt;anonymous&amp;gt; (typescript-extends-undefined-bug\out.js:13:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:901:3&lt;/code&gt;&lt;/pre&gt;

And when switching the argument file order, no error:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;$ tsc --out out.js Parent.ts Child.ts &amp;amp;&amp;amp; node out&lt;/code&gt;&lt;/pre&gt;

Typescript version 0.8.3.0. Node.js version v0.10.1.&lt;br /&gt;
&lt;/div&gt;</description><author>PSP2</author><pubDate>Sat, 18 May 2013 09:49:25 GMT</pubDate><guid isPermaLink="false">New Post: Single file output does not work with extends 20130518094925A</guid></item></channel></rss>