Skip to content

doc: replace NOTEs that do not render properly #57484

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

Merged
merged 1 commit into from
Mar 17, 2025
+7 −11
Merged

doc: replace NOTEs that do not render properly #57484

Show file tree
Hide file tree
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
12 changes: 4 additions & 8 deletions doc/api/cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -919,14 +919,10 @@ added: v23.10.0

> Stability: 1.0 - Early development

If present, Node.js will look for a
configuration file at the specified path.
Node.js will read the configuration file and apply the settings.
The configuration file should be a JSON file
with the following structure:

> \[!NOTE]
> Replace `vX.Y.Z` in the `$schema` with the version of Node.js you are using.
If present, Node.js will look for a configuration file at the specified path.
Node.js will read the configuration file and apply the settings. The
configuration file should be a JSON file with the following structure. `vX.Y.Z`
in the `$schema` must be replaced with the version of Node.js you are using.

```json
{
Expand Down
6 changes: 3 additions & 3 deletions doc/api/typescript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,9 @@ but we recommend version 5.8 or newer with the following `tsconfig.json` setting
}
```

> \[!NOTE]
> Use the `noEmit` option if you intend to only execute `*.ts` files, for example a build script.
> You won't need this flag if you intend to distribute `*.js` files.
Use the `noEmit` option if you intend to only execute `*.ts` files, for example
a build script. You won't need this flag if you intend to distribute `*.js`
files.

### Determining module system

Expand Down
Loading