[ASI-837] Allow typescript + javascript interoperability in content-node

[dmanjunath]

Description

Currently in content-node typescript was hard to integrate because we couldn't have something like
index.ts -> file.js -> new_file.ts where -> means requires()
to incrementally switch to TS.

However, with this option changed we can now have the above dependency graph.

Tests

Tested this locally and took it out to stage creator node 4 to make sure it compiles, comes up and serves requests.

I converted the hashids.js file to hashids.ts and added a log to tracks.js to print out the encoded id for 6. This demonstrates that ts can require a js file which can require another ts file with full interoperability

tracks.js

...
console.log("encode", encode(6))

logs

[nodemon] restarting due to changes...
[nodemon] starting `node --inspect=0.0.0.0:${debuggerPort} --require ts-node/register src/index.ts`
Debugger listening on ws://0.0.0.0:9230/fcd9455d-026f-4c13-873a-ee68b6ad0836
For help, see: https://nodejs.org/en/docs/inspector
Warning: configuration param 'awsBucket' not declared in the schema
configuration param 'awsAccessKeyId' not declared in the schema
configuration param 'awsSecretAccessKey' not declared in the schema
[2022-04-01T21:08:45.390Z]  INFO: audius_creator_node/946 on 4a6076489df1: Loglevel set to: debug
Fri, 01 Apr 2022 21:08:57 GMT sequelize deprecated The logging-option should be either a function or false. Default: console.log at node_modules/sequelize/lib/sequelize.js:196:13
encode AnlGe

How will this change be monitored? Are there sufficient logs?

Services won't start if there's a bug here. Health check would immediately identify this

[dylanjeffers]

great catch! looks like we need to update tests to be ts-compatible, maybe have to add ts-mocha? have a look in libs package.json for an example

[dmanjunath]

@dylanjeffers yes! i'm working on that now. thanks for paving the way 🙂

[dmanjunath]

these were never actually defined as variables and it was now throwing an error with ts-node

[dmanjunath]

this is the actual fix, confirmed by dylan with link to official tsconfig files https://github.com/tsconfig/bases/blob/main/bases/node16-strictest.combined.json#L10

[dmanjunath]

we have to omit the extension because locally it's reading the ts file but in the prod image it's using a transpiled version of js. the transpiled version should be 1-1 to the ts so functionally the same

[dmanjunath]

@dylanjeffers tests pass now, i also took it out to one of our stage content nodes and tested the new function that was moved to typescript so the transpile to the static build/ folder also seems to work. if you wanted to take one more look before merge

[dylanjeffers]

Looks great!