-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
@open-wc/scoped-elements v2.2.4 breaks lit module resolution #2728
Comments
I feel like there's an npm bug where it's not choosing a common version of a library only when there's an upgrade of one package. |
Interestingly, doing this is actually what originally put me in this broken situation 😅. Maybe npm version matters? I'm on npm v9.8.0, haven't tried v10 yet. |
Looks like I also need a |
Expected behavior
No problems with
lit
module resolution. (As the behavior in@open-wc/scoped-elements
v2.2.3)Actual Behavior
If
@open-wc/scoped-elements
v2.2.4 is installed, two different versions of@lit/reactive-element
get installed (v1.6.3 and v2.0.1) which confuseslit
and leads to the warning:Workaround
Either add
"@lit/reactive-element": "^1.6.3"
or"@open-wc/scoped-elements": "2.2.3"
to the"overrides"
field of yourpackage.json
file.Additional context
lit
v2.8.0 (outdated, but I didn't expect a patch version bump in@open-wc/scoped-elements
to break this)@lit/reactive-element
(Unable to resolve signature of property decorator when called as an expression) lit/lit#4305The text was updated successfully, but these errors were encountered: