Fix TS test running when project is first initialized with japa

[Barabasbalazs]

🔗 Linked issue

#6

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

When using this script with the TS options for initializing a project for example with the following method:

npm init japa@latest .

the npm run test command will throw some errors because:

1. It's using ts-node which has some old esm flags enabled
2. It does not initialize a proper tsconfig.json so the ts compiler does not know how to run the test command

So to fix this, the PR has the following changes:

1. Changed ts-node for ts-node-maintained, and updated the test command accordingly
2. Added @swc/core devDependency so the ts compiler can transpile the code
3. If the project is using TypeScript, the cli will create a basic tsconfig.json file with the following minimal settings:

{
   "compilerOptions": {
     "module": "NodeNext",
    }
}

this way the test command will run properly.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[Barabasbalazs]

@thetutlage I checked out why the pipeline failed and it seems that some of the dependencies like poppins/exception release-it don't support node v18.16.0 anymore, and that causes the pipeline to fail.

I updated the workflow files and the package.json accordingly, so it better reflects what version of node this project supports.

[thetutlage]

@Barabasbalazs Thanks for the PR. I think I missed it because I wasn't watching this repo notifications