Update ts-node for M1 support with workers

[mariusandra]

Changes

• Resolves yarn start:dev is hanging (running on M1) #370
• After these changes, the workers started again for me on my M1 Air.
• I was now running NodeJS 16.3, but I'd expect it to work on other versions.
• The TS update required some changes to a few places. Probably !! would have done the trick as well. Not sure why it errored there though, as value had undefined as one of its type options, so 🤷

Checklist

• Updated Settings section in README.md, if settings are affected
• Jest tests

[neilkakkar]

The undefined (and few others in tests) weirdness could be because:

WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.2.0

YOUR TYPESCRIPT VERSION: 4.3.2

Please only submit bug reports when using the officially supported version.

[mariusandra]

Good point. I bumped all the eslint packages as well.

[mariusandra]

This is trickier than I expected. I need to upgrade ts-node to v27 to fix those TS errors, but that requires at least NodeJS 14.15.0.

I have 14.5.0 installed and personally have no problem upgrading, but what about all our clients? What nodejs version are they running? I remember when we created the plugin server, a lot of customers said they had to explicitly upgrade their node versions to 14 for it to work. What frustrations will this change bring if they now have to upgrade to 14.15?

I hence limited ts-node to the latest v26. 🤞

[alexkim205]

Yes! Tested the branch locally and it works beautifully.

[mariusandra]

Great! Feel free to merge ;)