-
Notifications
You must be signed in to change notification settings - Fork 132
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
accessing types from semiotic v2 #527
Labels
chores 🧹
Infrastructure and updates
Comments
These are good points. I'll dig into it and see what I can do to clean this up. I've been working with typescript for a while but I'm still rather new to publishing types. Happy to review a PR if you want to dive into it. |
I believe this is now fixed by #594 and available in Warning: only named imports are now available. Use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using [email protected], I am able to access the types only when I import components by name from the
dist/
directory. This is a tricky thing to discover because the live code examples uselib/
.Types Included
Types Not Included
Thoughts
Is importing components by pathname the right pattern? It would be helpful to clarify dist vs lib, especially in the code examples on https://semiotic.nteract.io/.
Should I also be able to import components from the package index? Might need a
"types"
entry inpackage.json
.The text was updated successfully, but these errors were encountered: