Skip to content

Commit

Permalink
Merge pull request #248 from iambumblehead/update-resolver-improve-mo…
Browse files Browse the repository at this point in the history
…dule-resolution

update resolver to improve module resolution
  • Loading branch information
koshic authored Oct 8, 2023
2 parents 90e3e57 + 63d8680 commit 88eb17a
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# changelog

* 2.5.2 _Oct.06.2023_
* [update resolver](https://github.com/iambumblehead/esmock/pull/243) to improve module resolution. See resolvewithplus tags [v2.0.6](https://github.com/iambumblehead/resolvewithplus/releases/tag/v2.0.6) and [v2.0.7.](https://github.com/iambumblehead/resolvewithplus/releases/tag/v2.0.7)
* **resolve "exports" before "main".** The [spec says:](https://nodejs.org/api/packages.html#package-entry-points) _the "exports" field takes precedence over "main" in supported versions of Node.js._ The updated resolver correctly returns "main" before "exports" (older resolver did not).
* **use package.json "type" to return "import" or "require".** The older resolver did not read package.json type and returned incorrect "require" values for some packages. For example, if this [inferno package]( https://www.npmjs.com/package/inferno) where changed to use type "module", the older resolver would return "index.js" rather than "index.esm.js"
* 2.5.1 _Sep.13.2023_
* [resolve existing ".ts" files,](https://github.com/iambumblehead/esmock/pull/243) rather than ".js" files, when typescript detected, thanks @tpluscode
* 2.5.0 _Sep.09.2023_
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@
"node": ">=14.16.0"
},
"dependencies": {
"resolvewithplus": "^2.0.4"
"resolvewithplus": "^2.0.7"
},
"devDependencies": {
"c8": "^8.0.1",
Expand Down

0 comments on commit 88eb17a

Please sign in to comment.