Should I use Traceur instead of Typescript to target ES5 but be ready for ES6
I'm working on a large code base that could benefit from Typescript, but since eventually the world will be moving to ES6, should I steer the development towards Traceur?
I don't want to change Typescript implementations in order to target ES6 (when is ready), so my feeling now is to go ahead with Traceur.
Can anyone advise?
I definitely do not agree with the opinion that TypeScript and Traceur are so different, TypeScript is ES5 with types and Traceur is just about ES6.
On the one hand there is an ES6 compatible TypeScript 2.0 in progress. On the other hand there are a couple of features in Traceur marked as experimental in docs, namely types and annotations. And it turns out that types are very similar to the TypeScript types whereas annotations are something irrelevant both to ES6 and TypeScript. So Traceur is more just ES6 and there is already name for that: AtScript. Yes, we have another language extension :-)
There is a nice slide from Miško Hevery presentation that shows what is really going on here, fully valid as soon as TypeScript 2.0 is released:
So whatever you decide to use, it is important to note: they are subsets, you may write ES5/ES6 JS and it will be valid TypeScript code, you may write TypeScript and it will be valid AtScript code.
Turning back to your question, I would give the humble advise to start with ES6 using Traceur with experimental features turned off (it is pretty stable now) and extend as needed, because this is not so radical a decision, doesn't lock you in and leaves space to move in the future.
UPD: At the beginning of the 2015 I would also recommend to pay attention to 6to5 project (renamed to Babel) as an alternative to Traceur. It moves very fast and provides has some nice features, such as readability of generated code and better support for node.js and build systems.
- Route "/[locale]" used `params.locale`. `params` should be awaited before using its properties
- Uncaught TypeError: Typescript extension method not a function
- Typescript: Retrieve element type information from array type
- i18next + react router : My URL isn't changing correctly when language is switched
- Vue's ref doesn't maintain types of nested private properties
- Can I run a function after navigating to a new page and waiting for that page to finish loading?
- how to change angular stepper progress color when next step active
- Why does instanceof Observable return false in my tests?
- VS Code not doing type checking on typescript files
- Passing Gitbeaker API client between functions
- Consuming multiple properties via @Input() decorator in Angular 2
- Absolute Imports: React and Typescript
- Typescript: How can I make entries in an ES6 Map based on an object key/value type
- TypeScript's as const v JavaScript's Map object
- Jest/Typescript: Mock class dependencies containing private members in jest and typescript
- 'imports' is only valid on a component that is standalone
- NX Unable to complete project graph creation. Worker stopped with exit code: 1
- nest start removes my json files from dist
- TypeScript with React's useContext? property does not exist
- How can I infer the generic type parameters of a generic parameter in typescript?
- Converting Backbone structures to TypeScript
- How to fetch default action in +page.server.ts file in SvelteKit
- TypeScript recommended project structure with modules
- NestJS NATS request-response
- Is there a way to have a negative number as a key of an index signature?
- Testing vue3 computed properties with TypeScript SFC
- Axios return as specific type
- Arrow functions with untyped parameters resolve to undefined when inferring their types
- Wrap generic function
- find function isn't working properly in angular and firebase