Setting appRoot by combining project root and outDir

[ilDon]

The appRoot value is now based on the project root path and the value set in outDir, without taking into consideration the value in baseUrl.

In this way tspath calculates the dir to parse as the tsc transpiler does.

[Ansraer]

Thanks for making the pr, that's exactly what I have been doing in my local version for quite some time now. Really hope this gets merged into master soon.

[duffman]

This have been an issue for many of you :) I have to admit I have been a bit slow/lazy since this was originally crafted for my own local project structure :)

I will make sure this feature will be included in the next release, which is real soon, there are a number of other features that need to be committed as well!

Thanks guys for your contributions!

[duffman]

The latest version is using yargs for command line parsing and the params are now static (as your table) if we´re going to show help "screen" like this we should define the params in a collection which is then iterated for the help screen to avoid having to update the static text every time a param changes.

[duffman]

I´m sorry that I overlooked your suggestion here, this feature was actually implemented a while back in my dev branch, in other words, the actual feature suggestion was good :)

However, this is a very dirty piece of code, using a static reference since the engine have no knowledge of the tspath class which is where a command param should be parsed, if you study the code everything the engine works with is properties set from the creating class so it totally breaks the pattern I have used.

Also, by using strings like this quoting a param in this case would make it harder to maintain, let´s say a parameter change or is removed, then you not only have a bug, it´s harder to spot, if you ever do a hack like this, at least use constants.

[duffman]

A fix for the problem regarding the rel dist folder is available in v 1.3.5,