Migrating a 10,000-line legacy JavaScript codebase to TypeScript

Re:Migrating a 10,000-line legacy JavaScript codebase to Typ... by smt88 on Friday June 17, 2016 @02:56AM (#11921066)

You're talking about two different things. Haxe is a different language, while TS is a superset of JS (all JS is valid TS).

JS -> Haxe requires rewriting 10k lines before the program will run.

JS -> TS requires changing the file names, doing some imports, and adding "any" in a few places. The program will then run, and type information can be added gradually.

[ Parent | on HN ]

Re:Migrating a 10,000-line legacy JavaScript codebase to Typ... by nudpiedo on Friday June 17, 2016 @05:08AM (#11921474)

I do not see that much of differences between Haxe and JS, mostly because Haxe is a superset of EcmaScript. However the process is not that automatic because TypeScript is more permissive I would say (though there is already a convertor from typescript to haxe: ts2hx).

But that said, I am not really that much experienced with TypeScript.

[ Parent | on HN ]

Re:Migrating a 10,000-line legacy JavaScript codebase to Typ... by smt88 on Friday June 17, 2016 @10:06AM (#11922678)

According to Wikipedia, Haxe is not a superset of ES:

"Haxe is similar to ECMAScript, although almost no ECMAScript code will run on Haxe without modifications."

[ Parent | on HN ]

Re:Migrating a 10,000-line legacy JavaScript codebase to Typ... by sa_su_ke_75 on Friday June 17, 2016 @08:25AM (#11922185)

haxe have some incompatibility with syntax js. like don't support classic for and in if statement null must be explicited (you must do if (x==null)). but thanks to macros the porting of js generic more simple.

[ Parent | on HN ]