-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: minor clarification in modules api doc. #1983
Conversation
Mostly LGTM, but the proper language might be "relative path (i.e. |
@@ -145,7 +145,7 @@ A module prefixed with `'./'` is relative to the file calling `require()`. | |||
That is, `circle.js` must be in the same directory as `foo.js` for | |||
`require('./circle')` to find it. | |||
|
|||
Without a leading '/' or './' to indicate a file, the module is either a | |||
Without a leading '/', './', or '../' to indicate a file, the module is either a | |||
"core module" or is loaded from a `node_modules` folder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated-but-nearby nit: If you're feeling like it, "core module"
in the next line should really just be core module
without any quotation marks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
@Fishrock123 But documenting The purpose of this is to make the documentation at least consistent. |
Yeah. LGTM. |
LGTM |
PR-URL: nodejs#1983 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
This one is trivial. I noticed it while reading the
modules
API documentation.