Should have JavaScript knowledge before get into Typescript.
Microsoft made TS only for one reason, because all .net dev does not understand Java Script :), so learn JS, it always worth know basics :)
Leave TypeScript for now. Learn JavaScript and the DOM API first. TypeScript is just a tool, which extends the functionality of the JavaScript language (it's also know as superset). Mixing them together will introduce unnecessary complexity to your learning. So, start simple. Only when you have a deep understanding of the fundamentals of JavaScript and have built or worked on several medium to big projects, you can start exploring TypeScript and the surrounding ecosystem.
When you are ready, you may ask? If you can answer these questions:
Only then you are probably ready to start learning it.
I think, it is important to know where the language and paradigms are coming from and what you deliver to your clients, so I discourage learning TypeScript first. Knowing JS can help you with a lot of TypeScript problems and enables you to include JS files into TS without a problem.
However, I do not want to suggest that you become a master of JS first. It is enough if you understand basic principles about JS, so you can read, understand and solve problems in vanilla JS. If you still feel the urge to learn TypeScript as fast as possible, you can then switch over and immerse yourself.
There is no need to learn typescript explicitly until you are planning to work on Angular 2 /4 .
Typescript is good, forces you to write better JavaScript code, complies to JavaScript but, essentially not required for other frameworks.
ES6 is enough JavaScript to work on all libraries and frameworks.
I'm going to be bold and suggest learning JS (ES5) then skip Typescript and just learn JS ES6 + ES7 instead.
rozzzly
Insanity at its best - github.com/rozzzly
I'm going to go ahead and decent from the consensus by saying: it is okay.
TypeScript is JavaScript. You're still going to learn all the fundamentals of JavaScript, it's just going to be sugarcoated with type-safety.
However, I think it would be a bad idea to apply for a position looking for a JS dev if you've never actually written plain JavaScript. If you're writing TypeScript, you're almost certainly writing ES 2015+ syntax. There's a ton of ES5 (and below) code out there today in production so it's quite likely you'll run into it in the future.
Without strict typing and modern syntax, you'll probably be in over your head a little bit. Old JS blows! The days of jQuery were dark indeed. So I really suggest after you get the basics(let/const, types, loops, arrays, objects, classes, npm, etc) you make a concerted effort to go back and rewrite some of that same code in ES5. That will force you to understand prototypes, closures, the various class patterns, JavaScript's numerous quirks, etc. Once you have atleast a mild understanding of that, read into how babel and webpack work; that will make you a pro!
Starting off with TS might make the transition from a strictly typed language smoother, just don't neglect to learn about ugly bits.