Module entry point "nise.js" is wonky

[rotu]

package.json lists "module": "nise.js" as an entrypoint, but the nise.js file is a UMD module, not a ES module.

Additionally, the shape of the module when I use a ESM import is wonky. Here's what I get from Node CLI:

>>> await import("nise")
[Module: null prototype] {
  default: {
    fakeServer: {
      // ...
    },
    fakeServerWithClock: {
      // ...
    },
    fakeXhr: {
      // ...
    }
  },
  fakeServer: {
    // ...
  }
}

[fatso83]

Hi, thanks for this. The non-standard module field used by some bundlers is supposedly meant to point to a directory of ES Modules. I guess it might as well be better to simply remove it? With regards to the "shape", are you referring to the exported functions being available under the default export, instead of separate exports on the root?

[rotu]

Yep, the various options are kinda a mess to choose from. I think it should be using main and exports as documented here.

By the “shape”, I mean that fakeServer is the only option available to import by name. Either all 3 named exports should be there or none at all.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rotu]

not stale

[fatso83]

@mroderick Are you looking at this wrt your current ESM work?