You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using semiotic@2.0.0-rc5, 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 use lib/.
Types Included
import XYFrame from 'semiotic/dist/XYFrame'
Types Not Included
import XYFrame from 'semiotic/lib/XYFrame';
import {XYFrame} from 'semiotic';
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 in package.json.
The text was updated successfully, but these errors were encountered:
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.
When using semiotic@2.0.0-rc5, 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: