Skip to content

Releases: iambumblehead/resolvewithplus

wildcard-issue resolved

Choose a tag to compare

@iambumblehead iambumblehead released this 28 May 01:08
11bd11e

mostly resolves a recently-discovered issue resolving certain wildcard-pattern export keys

match exact export paths

Choose a tag to compare

@iambumblehead iambumblehead released this 01 Sep 13:19
a4c20a1

correctly resolve openai package

Choose a tag to compare

@iambumblehead iambumblehead released this 24 Jan 21:19
ef770ae

fix problem resolving the openai module

improve wildcard nesting expansion

Choose a tag to compare

@iambumblehead iambumblehead released this 26 Feb 18:40
0f680a2

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

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

Full list of changes,

resolve wildcard-using pattern resolution

Choose a tag to compare

@iambumblehead iambumblehead released this 23 Jan 19:27
d3e2912

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

resolves criticaal error

Choose a tag to compare

@iambumblehead iambumblehead released this 20 Oct 18:10
f22a56d

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

remove unused condition

Choose a tag to compare

@iambumblehead iambumblehead released this 19 Oct 21:39
0fa3bf3

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

support user-defined `priority` list

Choose a tag to compare

@iambumblehead iambumblehead released this 19 Oct 17:09
30ebb6a

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

Choose a tag to compare

@iambumblehead iambumblehead released this 15 Oct 15:29
1274be5

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 sort

Choose a tag to compare

@iambumblehead iambumblehead released this 11 Oct 18:41
c244cad

remove un-necessary sorting to provide faster lookups