That's a pretty odd question.
TypeScript is a superset of JavaScript. All valid JavaScript is syntactically valid TypeScript (though TypeScript may be stricter about type conversions). The goal of TypeScript is to add type semantics to JavaScript, aside from type-related features like interfaces and type aliases most syntax additions are either based on features recently introduced to JavaScript or features proposed to be added to the language (enums may be an exception to that though).
The main use of CoffeeScript is to allow Ruby programmers to avoid JavaScript. The goal of CoffeeScript was to create an alternative syntax for JavaScript that is more familiar to Python and Ruby developers and that takes away some of the traps of JavaScript and add some syntactic sugar that didn't exist in JavaScript at the time.
For most purposes, CoffeeScript has been superseded by modern JavaScript (which now includes features like classes and arrow functions), which has led to many people moving from CoffeeScript to plain JavaScript.
TypeScript on the other hand continues to provide benefits on top of JavaScript even as some of the experimental syntax features implemented in TypeScript become part of JavaScript itself. JavaScript won't have a type system like TypeScript's for the foreseeable future, so TypeScript will continue to be beneficial to developers looking for a little more compile time type safety in their JS.
As an alternative to TypeScript consider Flow, which defines itself as an addition to JS rather than an extension of it and has a slightly different philosophy to its type system but otherwise is very similar in purpose and use to TypeScript.
As an alternative to CoffeeScript consider other alternative JS based languages like LiveScript.