-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Type error in v13.1.1 #534
Comments
Not exactly the same fix since 13.x expose ParseObject and possibly other module exports, my suggestion migrate to 14.0.1 and use |
@evanjo03 once #535 is merged we can make PR to fix @joeattardi/emoji-button in the meantime adding Workarround:
|
Yep no problem! Appreciate you looking into this. Our team is pinning twemoji to version 13.0.0 temporarily and its working fine. |
That been said, I tried to fix "@joeattardi/emoji-button" with #535 but I get other errors due @FortAwesome update.
|
Type error when using version 13.1.1
Appears to the same problem described in this issue. Looks like a fix was applied for v14, but not for v13.
To Reproduce
Steps to reproduce the behavior:
npm init @open-wc
and follow promptscd [project-name] && npm i
npm i @joeattardi/emoji-button
import { EmojiButton } from "@joeattardi/emoji-button";
npm run tsc
Expected behavior
Tsc occurs without issues.
Screenshots
Environment
Chrome 99.0.4844.51
The text was updated successfully, but these errors were encountered: