add "exports" field to support newer module resolutions like node16

[samuelstroschein]

Setting the moduleResolution in the tsconfig to node16 results in no types being resolved.

I suppose the reason is a lacking exports field in package.json. See https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/#packagejson-exports-imports-and-self-referencing. I haven't tested it but expect the exports field to solve the bug + it's a good idea anyways.

With node16 module resolution (the new module resolution)

With nodenext module resolution (the default)

Here is a reproduction https://stackblitz.com/edit/typescript-3exolv?file=index.ts

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
shoelace	✅ Ready (Inspect)	Visit Preview	Nov 15, 2022 at 4:21PM (UTC)

[samuelstroschein]

On that note, shoelace requires node v14. The exports field is supported since node 12. It might be a good idea to get rid of the main, module and types field in package.json as they should be redundant.

https://nodejs.org/api/packages.html#packages_exports

[claviska]

Looks good to me. Thanks for jumping on this!

Did you want to update the PR to remove main | module | types as well? If not, I'm happy to handle it later today or tomorrow.

[samuelstroschein]

@claviska I refrained from updating the PR to remove main, module, types to not possibly break some things. I don't expect anything to break but propose that you remove those keys and see if everything works.

[samuelstroschein]

Whups just crossed my mind: The minimum TypeScript version would be 4.5 if types is removed.

[claviska]

Nice catch. I'll leave types but remove main and module then.

[samuelstroschein]

It would be helpful if you could release a new version. Otherwise, users of shoelace can't use moduleResolution: node16.