Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dedupe-mixin has DeprecationWarning No "main" or "exports" field #2495

Open
mservaising opened this issue Oct 17, 2022 · 1 comment · May be fixed by #2496
Open

dedupe-mixin has DeprecationWarning No "main" or "exports" field #2495

mservaising opened this issue Oct 17, 2022 · 1 comment · May be fixed by #2496

Comments

@mservaising
Copy link

At run time I get following error for dedupe mixin package
[DEP0151] DeprecationWarning: No "main" or "exports" field defined in the package.json

solution: Add export field.

mservaising added a commit to mservaising/open-wc that referenced this issue Oct 17, 2022
@riovir
Copy link

riovir commented Nov 17, 2023

The issue of breaking changes has been brought up for this kind of fix. As far as I see this issue has been addressed for @open-wc/scoped-elements like so:

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

Would it be acceptable if the @open-wc/dedupe-mixin followed suit and addressed it in a consistent manner?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants