Fix typo in --specifier-resolution=[node]#39249
Conversation
doc/api/esm.md
Outdated
| file. | ||
|
|
||
| The `--experimental-specifier-resolution=[mode]` flag can be used to customize | ||
| The `--experimental-specifier-resolution=[node]` flag can be used to customize |
There was a problem hiding this comment.
I don't believe this change is correct. "mode" here is referring to the parameter name, whereas "node" is one possible value for the "mode" parameter. The "mode" could also have a value of "explicit".
|
ohh got it, sorry about that :) mmm I guess maybe something different then mode? maybe |
from the very fact that this PR exists shows that the word /cc @nodejs/loaders |
|
I think PR update welcome |
|
Thanks for the comments! |
doc/api/esm.md
Outdated
| file. | ||
|
|
||
| The `--experimental-specifier-resolution=[mode]` flag can be used to customize | ||
| The `--experimental-specifier-resolution=[resolution-mode]` flag can be used to customize |
There was a problem hiding this comment.
This line now exceeds 80 characters, while the rest of the paragraph is wrapped at 80 chars. Not sure whether we usually fix this.
There was a problem hiding this comment.
Yes, it fails the lint doc check, which blocks merging.
There was a problem hiding this comment.
@tniessen in my anecdotal experience we usually fix this for first time contributors if they are unable to do so themselves.
benjamingr
left a comment
There was a problem hiding this comment.
Fix looks good - please drop it to two lines in order to meet the 80 character limit :)
|
The flag was removed in #44859. |
|
Sorry for dropping the ball on getting this through the finish line back then @Urigo ! Thank you for your contribution |
No description provided.