-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat: use Typescript in custom-media-element #51
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cca06ab
to
447e778
Compare
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.
Love it. Ship it.
], | ||
"type": "module", | ||
"main": "custom-media-element.js", | ||
"types": "custom-media-element.d.ts", | ||
"main": "dist/custom-media-element.js", |
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.
this will have ripple effects on CDN usage, right? do we need to account for that anywhere (in our owned projects, docs, comms, elsewhere)?
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.
good call. I think it's quite rare it's used via CDN. maybe for some examples and we tend to use the alias https://cdn.jsdelivr.net/npm/custom-media-element/+esm
it's easier to keep the type definitions up to date