Skip to content
Closed
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Update doc/contributing/maintaining-types-for-nodejs.md
Co-authored-by: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
  • Loading branch information
mhdawson and VoltrexKeyva authored Jul 29, 2022
commit 67ecbfa3fec79f8712d2a467cd77125878eb9ed8
2 changes: 1 addition & 1 deletion doc/contributing/maintaining-types-for-nodejs.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ and is as follows:

1. Users can ask Node.js to execute a file which is not one of the types it
can execute by default (.js, .mjs, etc.). For example `node script.ts`.
2. On startup Node.js will look for a config which is in the scope of the
2. On startup, Node.js will look for a config which is in the scope of the
file being executed.
3. If no config is found, Node.js will echo either:
* If the file was a TypeScript file, a TypeScript specific message with a
Expand Down