Skip to content
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.

Commit

Permalink
clarify URL resolution of package specifiers
Browse files Browse the repository at this point in the history
  • Loading branch information
guybedford committed Nov 5, 2018
1 parent b068ace commit a951b37
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/api/esm.md
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ The algorithm to resolve an ES module specifier is provided through _ESM_RESOLVE
> 1. Return _"node:${packageName}"_.
> 1. Set _parentURL_ to the parent folder URL of _parentURL_.
> 1. While _parentURL_ contains a non-empty _pathname_,
> 1. Let _packageURL_ be equal to _"${parentURL}/node_modules/${packageName}"_.
> 1. Let _packageURL_ be the URL resolution of _"${parentURL}/node_modules/${packageName}"_.
> 1. If the folder at _packageURL_ does not exist then,
> 1. Note: This check can be optimized out where possible in implementation.
> 1. Set _parentURL_ to the parent URL path of _parentURL_.
Expand All @@ -237,7 +237,7 @@ The algorithm to resolve an ES module specifier is provided through _ESM_RESOLVE
> 1. If _url_ is not _undefined_ then,
> 1. Return _url_.
> 1. Otherwise,
> 1. Let _url_ be equal to _"${packageURL}/${packagePath}"_.
> 1. Let _url_ be equal to the URL resolution of _packagePath_ in _packageURL_.
> 1. If the file at _url_ exists then,
> 1. Return _url_.
> 1. Otherwise, if _url_ is a directory then,
Expand Down

0 comments on commit a951b37

Please sign in to comment.