How to export typings from a node package #935
Replies: 3 comments 5 replies
-
|
I'm facing a similar issue. I'm bundling a third-party package that contains a file with several enums, each prefixed with the export keyword. However, after the bundling process is complete, all the enums are missing the export keyword. |
Beta Was this translation helpful? Give feedback.
-
|
Any solution for this yet? My file looks like this: import createClient, { ClientOptions } from "openapi-fetch";
import type { paths as Radarr } from "./generated";
export function createRadarrClient(clientOptions?: ClientOptions) {
return createClient<Radarr>(clientOptions);
}But the |
Beta Was this translation helpful? Give feedback.
-
|
You need to export the types in you index.ts file, without a export the tool dont know what should be exported |
Beta Was this translation helpful? Give feedback.
-
|
Wow, sorry about that 🤦 thank you! |
Beta Was this translation helpful? Give feedback.
-
|
So this works, but I'm still a bit confused as to why? I would imagine I should be able to export types from outside of just // a.ts
export interface INested {
foo: boolean
}
=====================
// index.ts
export * as a from "./a.tsI would expect I could then do the following but it doesn't seem to see that I exported import { type a } from "my-module"
const doThing = (args: a.INested) => { ... } |
Beta Was this translation helpful? Give feedback.
-
|
@prisis Any chance you could help explain why this doesn't work? |
Beta Was this translation helpful? Give feedback.
-
|
Hey :) tsup works different then tsc (from typescript), tsup need to know witch files you like to exports, because its use the rollup plugin (rollup-plugin-dts) or "@microsoft/api-extractor" (if you choose experimental dts) to generate the types for you, out of the defined files that you provided. Just as example without the exports https://github.com/visulima/visulima/blob/main/packages/fs/src/index.ts in this file, tsup wouldnt generated the types |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm, ok. Interesting! While a bit strange/less than ideal to me, since I can just re-export types from my index file it’s not a showstopper. I guess I just expected it to behave differently. Might dig into more later and see if there’s something I can config to work how I expected. Either way, thanks for the help! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm converting a node API wrapper package (not published on NPM, I just install it using the GitHub path but that doesn't matter I guess) for Aleph X-services to Typescript. I wrote a file
aleph.d.tswith typings for what the API returns (it responds XML and xml2js converts it to JS objects, which I need types for).The typings file looks like this:
Whenever I build that with tsup (with the
--dstflag), tsup removes theexportkeyword in the "dist/index.d.ts" file. The rest of the types is output as is to my dist folder, but not theexportkeyword, which makes it impossible to import these types from consumer projects. When I import the functions from same package in a Typescript file of a consumer project, types are inferred correctly (I can click to the definition), but in one case it is not, and I have to cast it manually which cannot be done if the Aleph namespace is not exported correctly.I found, I can just rename the file
aleph.d.tstoaleph.tsand addexport * from './aleph'to myindex.tsfile and everything works but that doesn't feel right as it contains only typings for the API response structure.Am I doing something wrong or is this a bug in tsup?
Beta Was this translation helpful? Give feedback.
All reactions