-
Notifications
You must be signed in to change notification settings - Fork 62
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
Types not working on import #103
Comments
Thanks. I'll look into it later. |
just deleting the |
|
adding |
Sorry for the late fix 😬 |
# [v4.1.2](v4.1.1...v4.1.2) (2023-07-14) ## 🐛 Bug Fixes - [`af8725f`](af8725f) properly export types (Issues: [`#103`](#103)) ## [4.1.2](v4.1.1...v4.1.2) (2023-07-14)
🎉 This issue has been resolved in version 4.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Unfortunately this is not fixed @flauwekeul, the package.json references a file located at "./dist/index.d.ts" but the file is actually located at "./src/dist/index.d.ts" Sorry haha ;D |
Ugh 😒 I should've tested it. Trying to fix it now. |
# [v4.1.3](v4.1.2...v4.1.3) (2023-07-14) ## 🐛 Bug Fixes - [`509f966`](509f966) Fix broken paths to types (Issues: [`#103`](#103)) ## [4.1.3](v4.1.2...v4.1.3) (2023-07-14)
🎉 This issue has been resolved in version 4.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
<3 |
Heya, ran into some issues trying out honeycomb-grid where imports didn't seem to be working right, which ultimately lead me to this thread.
I used patch-package to patch
[email protected]
as shown in the diff below. That got me going, but I'm not sure if that's actually the proper / ideal way to do it. Hopefully it gets you down the right path to a fix, though. This site from that thread gives some more info.This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: