chore: bump ts node

[jordanh]

Description

Dumps ts-node to facilitate a more useful REPL.

Demo

Loom: https://www.loom.com/share/0d3311fe7a5640c5a0e9d81781c7f6b9?sid=895f8705-f17d-4928-9f37-31ccd717e3a9

Testing scenarios

[Please list all the testing scenarios a reviewer has to check before approving the PR]

• Try REPL!

Run as:

DOTENV_CONFIG_PATH=<absolute path to your .env> npx -w parabol-server ts-node -r dotenv/config -O '{"noUnusedLocals":false, "strict":false, "noImplicitAny":false, "module":"NodeNext","target":"ESNext"}'

At the REPL prompt, try:

> import getKysely from './postgres/getKysely'
undefined
> const pg = getKysely()
undefined
> await pg.selectFrom('Team').select(['name','orgId']).where('id','=','6VSEcEuGdy').limit(1).execute()
[ { name: 'Company', orgId: 'Skc7syWwNox' } ]

Neat!

• Add to your VSCode task.json (⌘ + shift + p) -> Task: Open User Tasks and add to tasks array:

    {
      "label": "Start TypeScript REPL",
      "type": "shell",
      "command": "DOTENV_CONFIG_PATH=<absolute path to .env> npx -w parabol-server ts-node -r dotenv/config -r dotenv/config -O '{\"noUnusedLocals\":false, \"strict\":false, \"noImplicitAny\":false, \"module\":\"NodeNext\",\"target\":\"ESNext\"}'",
      "problemMatcher": [],
      "presentation": {
        "reveal": "always",
        "panel": "new"
      }
    }

• Run it with (⌘ + shift + p) -> Task: Run Task

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[jordanh]

It seems bumping this version of TS Node made a few more no implict: any buggies appear. This (and below) popped up when I was testing a migration

[mattkrick]

nice!
if you ever want to compile TS without checking for errors you can always run yarn sucrase-node instead of ts-node! it's pretty nice when just hacking away & not wanting to write perfect TS

[jordanh]

if you ever want to compile TS without checking for errors you can always run yarn sucrase-node instead of ts-node! it's pretty nice when just hacking away & not wanting to write perfect TS

TIL, thank you!