Checklist (for the issue creator)

[x] I have verified the bug exists in the latest version of @synergy-design-system/components (e.g. via pnpm install @synergy-design-system/components).
[ ] I can provide a simple, reproducible example of the issue (e.g. via code-sandbox or sample code, ...). --> Since this is about tooling, unfortunately not so simple 😳
[ ] I would be willing to provide a PR for this issue.

Version

The bug occurred with the following version of the component library: 2.4.3

Component

The issue arises when using the following component(s):

package.json

Environment

When building a depending application with eslint

Description

Eslint uses thenexports field of any packages to find declarations that an app may have imported and reports findings as a violation to the import/no-unresolved rule.

Unfortunatelly (at least in our version of eslint which is 8.22.0) it seems that eslint is not able to follow the exports/importfield as defined in the synergy components package:

  "exports": {
    ".": {
      "types": "./dist/synergy.d.ts",
      "import": "./dist/synergy.js"
    },
    "./custom-elements.json": "./dist/custom-elements.json",
    "./synergy.js": "./dist/synergy.js",
    "./synergy-autoloader.js": "./dist/synergy-autoloader.js",
    "./components/*": "./dist/components/*",
    "./utilities/*": "./dist/utilities/*",
    "./styles/*": "./dist/styles/*",
    "./themes/utility.css": "./dist/styles/utility.css",
    "./themes/*": "./dist/themes/*",
    "./translations/*": "./dist/translations/*",
    "./index.css": "./dist/styles/index.css"
  },

I already tried playing with this locally and it seems that it would be save to simply have a duplicate of your import field as default without breaking never tooling. This would allowed for older tooling to still find the correct exports:

"exports": {
    ".": {
      "types": "./dist/synergy.d.ts",
      "import": "./dist/synergy.js",
      "default": "./dist/synergy.js"
    },

Is this possible?

Acceptance criteria

[ ] The package.json of the exported @synergy-design-system/components package contains an exports/./default field that is a copy of the exports/./import field

synergy-design-system / synergy-design-system

fix: 🐛 Better tooling compatability in package.json #594