fix #14

When creating this PR, I make sure that I agree with the terms described in:

https://github.com/dtemplate/dev-template/blob/HEAD/CONTRIBUTING.md

When creating this PR, I make sure that I agree with the terms described in:

https://github.com/dtemplate/dev-template/blob/HEAD/CONTRIBUTING.md

fix #11

I could see that the tests are only written for some utils. I think it would be nice to write the tests for all utils runners and all files that execute a function.

Describe the bug

If you create a template that runs the cd example command (this in the run object that receives an array of objects) it doesn't work and the next commands continue to be executed in the same folder. does not make folder changes.

Code that caused the error

 {
  "name": "...",
  "version": "...",
  "description": "...",
  "successfullyMessages": [
    "..."
  ],
  "run": [
    "cd example"
  ]
}

Additional context

I think a cd:folderPath key could be created to solve this. But whoever has a better solution can comment here.

Describe the feature

Currently dt (dev-template) is not supporting writing templates in typescript.

Problems

The dev-template is written in typescript but the code that runs in the cli when they call dt in the terminal is a compiled code (ie javascript) so javascript will never understand typescript this because the typescript is typed what for javascript is an error typing

Solution

The only viable solution I could see was to add a new field in the template.json (file where the template data is in the template repository itself) with the name build for example, which is an array of strings. then make the CLI execute these commands (if any) and in these commands the template creators must pass the commands to build the template

example of new template.json:

{
  "name": "...",
  "version": "1.0.0",
  "description": "...",
  "build": [
      "tsc"
   ],
  "successfullyMessages": [
    "..."
  ],
  "run": [
    "..."
    "file:/dist/my-file-name.js"
  ]
}

Describe the bug

When dt runs a template it clones the template repository on github to the folder .dev-template/temp/{template-name} in the root where the command dt --template {do-name was executed -template}. But the TEMPLATE dependencies themselves are being installed in the root from where the command dt --template {template-name} was run, the idea is just the opposite, everything that has to do with templates should be in the folder .dev-template/temp/{template-name} and then it will be deleted. so that there is no remainder of the template that affects the structure of the project for the end user

Code that caused the error

dt --template **

Additional context

A big problem is if the same dependencies are used in the template and in the project that the template uses, basically it uninstalls the dependencies that the template uses, if this keeps happening and in a template use the TypeScript dependency and the project that the template generates use also have TypeScript. after the template process the typescript will be uninstalled. this because dt will understand that the typescript is a dependency of the template