Add TypeScript support and fix config bug

[robert-orlinski]

Hi!

I am a huge fan of this flat components' structure and this simple CLI. Also, I am a huge fan of TypeScript and the lack of support for this language was a little pain for me when it comes to that utility.

That's the reason for this PR 😌

Added:

• TypeScript support;
• Some README tweaks that explain new features.

Fixed:

• config's object assign, because of which custom configs weren't working.

Hope it will be useful!

[yasinkavakliat]

@joshwcomeau Would really love to get this merged as I only use TypeScript these days. Wanted to use this utility for a project, but I refuse to use plain JS 😄

[matt123miller]

@robert-orlinski @Coupz I'm using version 4.0.1 and it works for me. I originally came here to update the README to mention it supports TSX, mine is configured for TSX via the JSON file which is located in my home directory.

❯ cat ~/.new-component-config.json
{"extension":"tsx"}

I also just changed that to "ts" and created a quick component, it worked fine.

I also checked using the -x flag as shown and that all worked fine:

Seems to work for whatever value you provide so wanna try again on your machines?

[yasinkavakliat]

I've just tested it again, completely new installation of new-component and it still generates .js files for me @matt123miller
I'm on Windows, maybe that is the difference?

Edit: it works with the -x tsx flag and I've only created the config file in the root directory of my app.

[matt123miller]

Ah, I'm on mac. Maybe it is a Windows issue?

To clarify do you mean that it works with the config file at the root of your app? Or it doesn't and is only respecting the -x flag?

[yasinkavakliat]

Exactly. It ignores the config file and only respects the -x flag.

[fmdiaz]

Exactly. It ignores the config file and only respects the -x flag.

The same for me in Linux (Ubuntu 20.04). Tried both local project and global locations for the config file.