resolvewithplus

Essentially, this release enables resolvewithplus to resolve the following esm export

{
  "exports": {
    "./*": {
      "require": "./*.js",
      "import": "./*.js"
    }
  }
}

Full list of changes,

• add tests for path pattern resolver
• resolve more nested export wildcard-scenarious

resolve nested exports defined on named-properties with wildcards, eg exports: { './*': { default: './src/*/index.js' } } resolves this issue at esmock

resolve full path from package.json "main", "browser" and "module" definitions. resolves this issue at esmock.

remove unused condition and resolved error where fileurl path was not correctly resolved for package.json "main", "browser" and "module" definitions

when user-defined priority list includes "import" return packagejson.module before packagejson.main

support user-defined priority list when resolving nested export expressions

resolve error preventing module resolution. There is a condition that alters lookup paths for the situation when resolvewithplus is being developed and tested from inside another package's node_modules. The condition caused lookup errors. The condition was changed and a unit-test added

remove un-necessary sorting to provide faster lookups

use package type to determine lookup: 'import' or 'require'

(wiki is updated with details)

With this release resolvewithplus supports optional isbrowser, istypescript and isimport fields and when one of these is specified the resolver prioritizes browser-exported files, typecript and module files. By default, isimport is true

resolvewithplus('react-dom/server', '/resolvewith/test/', {
  isbrowser: true
}) // 'file:///resolvewith/node_modules/react-dom/server.browser.js'

resolvewithplus now also supports an advanced priority option. When a package.json is parsed, a default priority list determines the priority of named-exports in this order: browser (if isbrowser), then import then node then default. Define a custom priority list to specify a custom ordering. If you are using nodejs, this is probably not needed,

resolvewithplus('react-dom/server', '/resolvewith/test/', {
  priority: ['deno', 'default']
}) // 'file:///resolvewith/node_modules/react-dom/server.deno.js'

resolvewithplus('react-dom/server', '/resolvewith/test/', {
  priority: ['browser', 'default']
}) // 'file:///resolvewith/node_modules/react-dom/server.browser.js'

changelog:

• add support for 'priority' configuration option
• explicitly prioritize "browser" then "import" then "default", when browser and import both true
• update README image link to use "main" repo path
• replace reducer function w/ simple recursion

this PR changes the location of isTypescript detection to occur in one place that is more widely used so that it can be engaged more frequently to improve typescript resolution.

• improve resolution of typescript moduleIds

When the resolver detects a typescript parent it can apply typescript conditions to resolve the moduleId. New conditions can be added for typescript situations as needed, this new behaviour is a starting point,

• pin node 20.4 at unit-test pipeline, last version of node before import.meta.resolve was reduced
• add workspaces unit-tests
• add detection of ".ts" parent extension for applying typescript conditions
• use moduleId and parent as internal names, following nodejs

v2.0.2 use node v20 ci, increment dependencies

resolve windows modules with correct drive letter using patch from @mshima

return encoded url same as import.meta.resolve ,

• this, 'file:///path/to/indexfile/file%20name%20with%20spaces.js'
• rather than, 'file:///path/to/indexfile/file name with spaces.js'

Add test and changes to support import.meta.url parent. While exploring changes at esmock, it was discovered that esmock slightly modifies import.meta.url from the callee before passing along when calling resolvewithplus,

resolvewithplus('../../index.js', import.meta.url)

minified resolvewithplus.js is 50% smaller and total install size becomes 5.78kB, from 6.79kB

Returning fileurl-formatted paths allows esmock to be simplified, where esmock previously needed to detect and convert resolvewithplus paths to fileurl-formatted paths. Returning fileurl-formatted paths also makes resolvewithplus more interchangeable with import.meta.resolve, which also returns fileurl-formatted paths,

• return fileurl paths, following the behaviour of import.meta.resolve
• added tests around export sugar esm patterns

completed esm pattern parsing (big improvement)

resolve "pg" package's cjs "main": "./lib"

support win32 drive-style module-path