Echo JS 0.11.0

<~>

avi.vahl 2131 days ago. link 2 points
It's quite similar to ts-node... which I have also used over the years. I had quite a lot of trouble with the way it picked up configuration and @types packages, and the various Windows-only breakages. 

At a certain major version, they disabled the type checking by default. It might be enabled again in v6. Not sure.

Anyhow, as I needed the multiple tsconfig support (see README; "why?" section), I went ahead and created this library. Wanted to master TypeScript's language services further and learnt a lot in the process. I am also quite happy with the tests of source-map support and type isolation.
 
I plan further refactorings before v1.0.0... maybe even package names: `node -r ts-support my-script.ts`

I'll add a link to `ts-node` in the README.
KATT 2124 days ago. link 1 point
https://github.com/TypeStrong/ts-node#configuration-options

> You can set options by passing them before the script path, via programmatic usage or via environment variables.
> 
> ```
> ts-node --compiler ntypescript --project src/tsconfig.json > hello-world.ts
> ```

Never had the need but it seems to have a `--project` setting. Anyway, I'm sure you'd find a way to work with `ts-node` if you could, so it's no criticism, just curiosity! 🍻
avi.vahl 2122 days ago. link 1 point
Specifying a *single* tsconfig does not fit my current use-case, thus me making this project.

I wanted a solution that "simply works" for me (no configuration needed). It ended up as something that could assist others, so I published it as open-source. :)