Shebang support

[nevir]

Would be awesome to be able to use ts-node as a shebang script:

#!/usr/bin/env ts-node
console.log('ohai from TypeScript');

[blakeembrey]

@nevir Works for me, what's your issue?

[blakeembrey]

Closing as it appears to work.

[ghost]

This doesn't seem to work when the file is without an extension for whatever reason. Thoughts?

[blakeembrey]

It works but you will need the .ts extension. See #116.

[b1zzu]

Also if you don't want to install ts-node globally:

#!/usr/bin/env -S node -r "ts-node/register"

[ORESoftware]

without the ts extension, I assume you could do something like

#!/bin/bash
ts-node whatever

[VanTanev]

A bit more complete version of @ORESoftware's example above:

#!/usr/bin/env bash
/usr/bin/env ts-node whatever.ts "$@"

[troywweber7]

What's the best way to add the project flag to the shebang?

[cspotcode]

Pretty sure it's in the readme. I'm on mobile at the moment.

…

On Sun, Jun 28, 2020, 5:10 PM Troy ***@***.***> wrote: What's the best way to add the project flag to the shebang? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#73 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OHP7F47FC3T37FSA3LRY6WWFANCNFSM4B5ZUA3A> .

[troywweber7]

Ahh. I see. I need to use ts-node-script. So in an Nx project, if I'm making a publishable lib, it creates 2-3 tsconfig files. Obviously, when it is published node would run the CLI, but for testing purposes, I was thinking it would be nice to run it with ts-node from inside the same mono-repo... It might not pick up the tsconfig.lib.json, but it should pick up the tsconfig.json and if that isn't good enough, I can probably just build it before using it in mono-repo.

[cspotcode]

Yeah, we also let you override some "compilerOptions" within a tsconfig's `"ts-node": {}` object. So you can tell the compiler to behave differently in ts-node if needed. I think this is in the readme too, but if you find the readme is insufficient, feel free to file a ticket so we can improve it.

…

On Sun, Jun 28, 2020, 5:33 PM Troy ***@***.***> wrote: Ahh. I see. I need to use ts-node-script. So in an Nx project, if I'm making a publishable lib, it creates 2-3 tsconfig files. Obviously, when it is published node would run the CLI, but for testing purposes, I was thinking it would be nice to run it with ts-node from inside the same mono-repo... It might not pick up the tsconfig.lib.json, but it sounds pick up the tsconfig.json and if that isn't good enough, I can probably just build it before using it in mono-repo. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#73 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OHUSAKJ3HZMESZLU63RY6ZJZANCNFSM4B5ZUA3A> .

[micalevisk]

another one

• with flags
• with tsconfig-paths
• using npx (so you don't need to install ts-node globally)
• using another tsconfig.json file

#!/usr/bin/env -S TS_NODE_PROJECT="src/tsconfig.json" npx ts-node --transpile-only --files -r tsconfig-paths/register

const foo: string = 'bar'
console.log(foo)

[cspotcode]

You can also move the transpileOnly, files, and -r into your src/tsconfig.json, which simplifies the shebang to:

#!/usr/bin/env -S npx ts-node -p ./src/tsconfig.json

If the script is already within the ./src/ directory, then you can even omit -p.

[nocke]

I had luck with

sudo ln -sf ~/.npm-global/bin/ts-node /bin/ts-node

thereafter #!/bin/env ts-node works.

• as does #!/bin/ts-node which is closer to #!/bin/bash, but I would stick with the above, since is more common and others are less likely having to adapt it.
• nb1: I am aware, that /bin ist just a link to /usr/bin probably on most linuxes, just a cosmetic choice where to link to.)
• nb2: If someone works with ts-node under a different account on your machine, he might encounter rights issues from this linking into a personal folder. Unless you are suffently generous with chmod on your ~/.npm-global.
• I am not using nvm (figured out it cost me 2-3 seconds whenever opening a new terminal tab.), plain node 18.x