Skip to content

doc: fix grammar and phrasing in typescript.md #66977

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.

Sign up for GitHub

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

Open
ravi-arnan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

doc: fix grammar and phrasing in typescript.md #66977

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/api/typescript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ changes:
description: Type stripping is now stable.
-->

By default Node.js will execute TypeScript files that contains only
By default Node.js will execute TypeScript files that contain only
erasable TypeScript syntax.
Node.js will replace TypeScript syntax with whitespace,
and no type checking is performed.
Expand Down Expand Up @@ -164,7 +164,7 @@ namespace TypeOnly {
}
```

This will result in [`ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX`][] error:
This will result in an [`ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX`][] error:

```ts
// This namespace is exporting a value
Expand Down Expand Up @@ -231,9 +231,9 @@ is highly discouraged.
Stripping types inside `node_modules` is intended only
for local development.

### Paths aliases
### Path aliases

[`tsconfig` "paths"][] won't be transformed and therefore produce an error. The closest
[`tsconfig` "paths"][] won't be transformed and will therefore produce an error. The closest
feature available is [subpath imports][] with the limitation that they need to start
with `#`.

Expand Down
Loading