resolve named-properties that are also asterisk folder name

[iambumblehead]

cc @koshic (also @dschnare)

This PR is for resolving iambumblehead/esmock#289 eg, importing a moduleId "mymodule/mystuff" should return "mymodule/src/mystuff/index.js" given the below "mymodule" package.json,

{
  "name": "mymodule",
  "type": "module",
  "exports": {
    "./*": {
      "default": "./src/*/index.js",
      "types": "./types/*/index.d.ts"
    }
  }
}

While changes here may not be great, they only occur inside specific conditions that would currently fail every time. A few function calls were updated to include the "opts" param, beecause "opts" are needed by the esmparse function which is called in new place here.

First, the script checks to see if the property name includes an asterisk and if the definition is an object

if (isobj(esmval) && esmkey.includes('*')) {
  // ...
}

If that condition is true it generates an "expanded" version of the spec. eg, for moduleId "stuff",

{
  default: './src/mystuff/index.js',
  types: './types/mystuff/index.d.ts'
}

and tries to resolve the moduleId using the "expanded" spec value

esmparse({
  default: './src/mystuff/index.js',
  types: './types/mystuff/index.d.ts'
}, 'mystuff', opts) // ./src/mystuff/index.js

[iambumblehead]

on second look, there might be better ways I can think of for doing this one... maybe tomorrow I can try something else

[dschnare]

I'm not sure this will support multiple occurrences of * on the "right side".

All instances of * on the right hand side will then be replaced with this value, including if it contains any / separators.

// import { stuff } from 'my-module/stuff' <-- should resolve to "my-module/src/stuff/some-folder/stuff/index.js"
{
  "name": "my-module"
 "exports": {
    "./*": {
      "default": "./src/*/some-folder/*/index.js"
    }
}

[iambumblehead]

There are multiple situations that aren't handled here now and if there's no objection, maybe this area could be improved with follow up PRs that each have their own unit-test.

I google searched multiple wildcard exports last night and found reports of differences and some breakage between typescript and different runtimes. This seems like a feature that is not commonly used.

[iambumblehead]

eg, this would be another situation that wouldn't be expanded correctly here now (which is probably "okay")

{
  "name": "my-module"
  "exports": {
    "./feature*": {
      "default": "./src/features-*/index.js"
    }
}

[iambumblehead]

going to merge and publish this now. if any changes or suggestions or needed they can be applied with follow up MRs

[dschnare]

@iambumblehead Thanks for resolving this and moving so quickly. I appreciate the time you spent on this.

[iambumblehead]

@dschnare thank you I'm very happy if I can be a useful person :)

[iambumblehead]

@dschnare it would interesting if the asterisk-matching/expanding behaviour were updated to work in a robust way...