-
Notifications
You must be signed in to change notification settings - Fork 788
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
Feature/api extractor #32
Conversation
This is generated into the dist folder now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, rolled up definition file is much nicer. I technically only need the framer-motion.api.json
but the framer-motion.api.ts is quite nice to see the exported surface.
@@ -56,6 +56,7 @@ | |||
}, | |||
"dependencies": { | |||
"@emotion/is-prop-valid": "^0.7.3", | |||
"@microsoft/api-extractor": "^7", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets tag this at 7.0.13
to ensure the output is the same as Library.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But that should be in the yarn.lock, right? I'll make sure that will say 7.0.13, because I think it's at 17 now
scrollYProgress: import(".").MotionValue<number> | ||
} | ||
|
||
// (No @packageDocumentation comment for this package) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this everything? Feels a little incomplete...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this was everything api-extractor was complaining about, but I will double check
This now generates:
And:
@aron can you verify that this is what we actually need?