Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changed all references to ts-node consistent #1481

Merged
merged 2 commits into from Oct 3, 2021
Merged

changed all references to ts-node consistent #1481

merged 2 commits into from Oct 3, 2021

Conversation

animafps
Copy link
Contributor

@animafps animafps commented Oct 1, 2021

fixes consistency issues with ts-node references described in #1317

  • All references are ts-node except when explicitly referred to in the context of the usage of the CLI which is ts-node

Copy link
Collaborator

@cspotcode cspotcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I marked a couple places where I think the backticks are still appropriate, but I can make those changes before merging.

@@ -17,7 +17,7 @@ Hello, Ronald!

## Via tsconfig.json (recommended)

`ts-node` automatically finds and loads `tsconfig.json`. Most `ts-node` options can be specified in a `"ts-node"` object using their programmatic, camelCase names. We recommend this because it works even when you cannot pass CLI flags, such as `node --require ts-node/register` and when using shebangs.
ts-node automatically finds and loads `tsconfig.json`. Most ts-node options can be specified in a "ts-node" object using their programmatic, camelCase names. We recommend this because it works even when you cannot pass CLI flags, such as `node --require ts-node/register` and when using shebangs.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "ts-node" should still be in backticks since it's JSON syntax.

@@ -11,7 +11,7 @@ Here is a brief comparison of the two.
| Write native `import` syntax | Write native `import` syntax |
| Transforms `import` into `require()` | Does not transform `import` |
| Node executes scripts using the classic [CommonJS loader](https://nodejs.org/dist/latest-v16.x/docs/api/modules.html) | Node executes scripts using the new [ESM loader](https://nodejs.org/dist/latest-v16.x/docs/api/esm.html) |
| Use any of:<br/>`ts-node` CLI<br/>`node -r ts-node/register`<br/>`NODE_OPTIONS="ts-node/register" node`<br/>`require('ts-node').register({/* options */})` | Must use the ESM loader via:<br/>`node --loader ts-node/esm`<br/>`NODE_OPTIONS="--loader ts-node/esm" node` |
| Use any of:<br/>ts-node CLI<br/>`node -r ts-node/register`<br/>`NODE_OPTIONS="ts-node/register" node`<br/>`require('ts-node').register({/* options */})` | Must use the ESM loader via:<br/>`node --loader ts-node/esm`<br/>`NODE_OPTIONS="--loader ts-node/esm" node` |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be in backticks since it refers to the binary's name?

have one. If you are unsure which configuration is used, you can log it with `ts-node --show-config`. This is similar to
`tsc --showConfig` but includes `"ts-node"` options as well.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto previous comment about "ts-node" as JSON syntax.


**Note:** If you need to use advanced node.js CLI arguments (e.g. `--inspect`), use them with `node -r ts-node/register` instead of the `ts-node` CLI.
**Note:** If you need to use advanced node.js CLI arguments (e.g. `--inspect`), use them with `node -r ts-node/register` instead of the ts-node CLI.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto question about ts-node referring to the binary's name.

@cspotcode cspotcode merged commit b7162ab into TypeStrong:docs Oct 3, 2021
@cspotcode
Copy link
Collaborator

@animafps Thank you!

cspotcode added a commit that referenced this pull request Oct 11, 2021
* upgrade typedoc (#1454)

* update esm messaging in docs (#1455)

* Update vscode debug config (#1466)

* changed all references to ts-node consistent (#1481)

* changed all references to ts-node consistent

* Pesky maintainer-prerogative nitpicks

Co-authored-by: Andrew Bradley <cspotcode@gmail.com>

Co-authored-by: Anima <18208134+animafps@users.noreply.github.com>
@cspotcode cspotcode added this to the 10.3.0 milestone Oct 11, 2021
@cspotcode cspotcode mentioned this pull request Oct 11, 2021
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants