Pacharapol Withayasakpunt One of the way is indeed using threads.js (and observable-fns), but I came with a Native way (for Node 10+ latest with CLI --experimental option and Node 12+).
That is using tsc-watch instead of ts-node-dev.
Pacharapol Withayasakpunt This might not be something so special, but I bet not everyone knows.
*.ts files directlyUse ts-node instead of node, and ts-node-dev instead of nodemon.
Cannot run ts-node due to import syntaxes? No problemo, try this
ts-node -O '{"module": "commonjs"}' scripts/example.ts
I do not recommend you use ts-node in production.
Pacharapol Withayasakpunt It starts with inter-op with mongoose, and inspired from Typegoose.
It is an ORM that
For Mongo-like query, it can be tested here -- https://q2search.herokuapp.com/LiteORM (The actual Mongo-like query is in the console)
Pacharapol Withayasakpunt As a lover of TypeScript InteliSense and Vue, I have always tried to use TypeScript in Vue, but Vetur isn't as smart as it should...
*.ts.So, I have found some fixes --
Pacharapol Withayasakpunt Do you know that Visual Studio Code itself can auto-fix your code on save, to be compatible with linting rules.
Currently, I auto-fixes TypeScript, JavaScript, Vue, Markdown files.
For TypeScript, JavaScript, Vue; I simply use ESLint (there is TSLint, but it is becoming deprecated). VSCode ESLint might also be required
For Markdown, it is a little different. I use VSCode MarkdownLint to auto-fix on save.