-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Generate types for bundles #3385
Comments
Also related #2934 as the bundle should output referencing its types. |
I'm trying to use Deno for writing a library that should be compatible with Node after bundling. Is there any way that I could help with this issue @kitsonk? |
* chore: move test/index.js to mod_test.ts * chore: move test/typings.ts to typings_test.ts * test: format typings_test.ts with deno * test: refactor mod_test.ts to use Deno test * fix(AssertionError): make stack argument optional * build: use deno in build scripts * test: drop test index.html * build: add .tool-versions * build: add coverage folder to gitignore * build: add index.js to gitignore * style: deno fmt * build: drop dist files from package.json * style: deno fmt md files * style: deno fmt package* * build: move dist/mod.d.ts to index.d.ts * refactor: manually write index.d.ts for now Refs: denoland/deno#3385 * build: fix npm files * test: temporarily pass the typings tests * build: add deno ci * build: use denoland/setup-deno * style: deno fmt * build: remove tsconfig Not needed for Deno * build: remove broken coverage assertions * build: remove node build * style: fix all lint errors * fix(AssertionError): captureStackTrace inside consturctor * build: use deno lint * style: deno fmt * style: NAUGHTY DENO
Need this. |
Is there any progress on this? To make migrating to deno fesible I need a way of generating .d.ts file. |
No, there hasn't been progress due to other priorities. |
@kitsonk Is there any way to help on this? I've made a couple of spikes using deno as the primary dev tool for some of our libraries, and this is the only thing holding us back from pulling the trigger and making it the way to go. If there's a place to get started, or some attempts that have already been made then perhaps I could have a look? |
For those coming here looking to develop their library in deno, but still publish to npm, here is a really nice tool that got me up and running quite quickly. |
Are you missing a link here? :) |
Here it is: https://github.com/fromdeno/deno2node |
I was thinking about https://github.com/denoland/dnt Offical, good defaults but configurable |
@UltiRequiem Officials, too: denoland/dnt#2 (comment) |
Official too denoland/dnt#2 (comment) 😆 And that was months ago! I recommend dnt over deno2node |
I just meant that using |
🤦♂️ It was the seems very promising so far… |
|
With #3352, bundles are going to be a mechanism to distribute "libraries" in Deno. It is logical that someone might want to use a distribution bundle in another Deno workload (or consume it in other runtimes) and would want to have type safe consumption of those files, therefore we should generate the declarations along with a bundle.
Related to #2475.
The text was updated successfully, but these errors were encountered: