Asking for help about exporting TS types another way

ibc · October 10, 2024, 12:15pm

Hi, I’d like to get some feedback/help regarding this ongoing PR:

github.com/versatica/mediasoup-client

Export TS types in a separate entry point via 'mediasoup-client/types'

versatica:v3 ← versatica:export-types-as-a-separate-entry-point

opened 12:13PM - 10 Oct 24 UTC

ibc

+14 -4

## Details The idea is that, instead of exporting types like this: ```ts …import { types as mediasoupClientTypes } from 'mediasoup-client'; ``` We import them this way: ```ts import types as mediasoupClientTypes from 'mediasoup-client/types'; ``` ## TODO 1 I've briefly tested this and it looks like for this to work, the parent application must have in its `tsconfig.json`: ``` "module": "nodenext", "moduleResolution": "nodenext", ``` Is this ok? Any other implications? ## TODO 2 Should we stop exporting `types` from 'mediasoup-client' and instead force applications to import them from 'mediasoup-client/types'? ## TODO 3 We should export `HandlerInterface` type so applications do not need to do this ugly thing: ```ts import { HandlerFactory as MediasoupClientHandlerFactory } from 'mediasoup-client/lib/handlers/HandlerInterface'; ```

Thanks a lot!

Topic		Replies	Views
How do I use mediasoup-client with TypeScript and bundlers? mediasoup libraries	3	1766	January 25, 2021
Mediasoup typescript types not exported mediasoup libraries	3	83	September 6, 2024
TypeScript errors in mediasoup-client mediasoup libraries	3	963	January 17, 2021
Pure js for front end Integration	13	1381	August 10, 2021
mediasoup-client doesn't compile on Typescript 4.3 mediasoup libraries	2	355	May 28, 2021

Asking for help about exporting TS types another way

Related topics