exports map should have a main entry point

[thescientist13]

The current exports map configuration does not include a main entry point as a default resolution
https://github.com/lxsmnsyc/seroval/blob/main/packages/plugins/package.json#L53

Per the NodeJS docs, if additional subpath patterns are used, there should at least be a default entry point
https://nodejs.org/api/packages.html#subpath-exports

{
  "exports": {
    ".": "./index.js",
    "./submodule.js": "./src/submodule.js"
  }
}

Not having this this will cause APIs like import.meta.resolve to fail

ERROR (ERR_PACKAGE_PATH_NOT_EXPORTED): unable to resolve specifier => `seroval-plugins`

For comparison, the main seroval package has one

---

I think the simplest solution would be just pointing to the same entry point as import, already being used for ./web, e.g.

"exports": {
  ".": "./dist/esm/production/web.mjs",
  "./web": {
    // ...
  }
},

Happy to submit a PR if desired!

[lxsmnsyc]

Sorry since I've set this up like a year ago, was this necessary even if the package itself doesn't have a main file?

[thescientist13]

The docs indicate this feature was added back in Node 12.7.0, so presumably it was the case from the beginning.
https://nodejs.org/docs/latest-v12.x/api/packages.html#packages_subpath_exports

and import.meta.resolve has been around just as long
https://nodejs.org/api/esm.html#importmetaresolvespecifier

[lxsmnsyc]

What I mean is if a root path in the exports should be defined for subpackages to work?

Because seroval-plugins only has seroval-plugins/web, seroval-plugins doesn't do anything.

[thescientist13]

I don't think it breaks the sub packages per se, but not having one is not per "the spec" is my understanding, hence it causes import.meta.resolve to error out.