-
-
Notifications
You must be signed in to change notification settings - Fork 203
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) make it possible to pass additional file paths to emitDts #1412
base: master
Are you sure you want to change the base?
Conversation
Needed when someone uses the svelte.JSX typings. Closes sveltejs#1405
Marking this as draft because different thought just occured to me:
cc @jasonlyu123 |
From what I see the |
Oh right you're correct, that wouldn't work for you in this case. You could add a |
Wondering if there was any movement on this, or did you end up solving this in a different way? |
FWIW, I'm working on a Svelte component library, and we're compiling the Svelte components to web-components. We're using Currently, I have a fork of |
The plan is to move the element typing to the svelte core. You can see the roadmap here #1552 |
Okay, got this working without the |
Since Svelte 3.55 it's possible to enhance from HTML typings through the |
Needed when someone uses the svelte.JSX typings.
Closes #1405
Other possibilities:
string
like in (feat) Add support for svelte-jsx.d.ts and svelte-native-jsx.d.ts to emitDts #1405 -> decided against that because it's not flexible enough for other use casesrequire.resolve
for this to get thed.ts
file -> decided against that because people might use this in other environments than HTML (Svelte Native) and they couldn't pass their file in then