-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
path.resolve: clarify the example #25542
Comments
👍
👍 |
+1 to this. It could use some clarification. |
YakovL
added a commit
to YakovL/node
that referenced
this issue
Jan 20, 2020
see nodejs#25542 for details Fixes: nodejs#25542
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://nodejs.org/api/path.html#path_path_resolve_paths states:
This is something a bit diffucult to grab when in hurry (first though is: why that wouldn't be
/foo/bar/baz
?). One thing is "prepend" is meant not literally (otherwise that would be/barbaz
). The other is the whole idea is not very usual. My suggestion is to expand this into:But may be this is trivial for others, so I'd like to get some feedback before creating a PR.
The text was updated successfully, but these errors were encountered: