Types: Fix importing non-default types

[orgads]

Fixes #181.

[orgads]

Please notice I created 3 separate commits.

• Remove declare module and reformat the file with 2 spaces.
• Fix missing or wrong types.
• Fix the export issue.

[orgads]

@davehorton @danvirsen @hadar-laguna

[orgads]

Wait. This works with ESM, but breaks CJS :(

I'll try to fix this.

Forget it, it works fine in CJS, and in TS/CJS it works if you enable esModuleInterop.

[danvirsen]

After a quick test this seems to work fine. At least my project isn't complaining when I switch from my PR to this 🙂.

Last week I did however run into an issue with the types "parseUri" function, so if you could update that as well I think that I can close my PR in favour of yours.

I use the following locally, but I haven't had the energy to check if any values could be null or something else in some cases.

export function parseUri(uri: string): {
    scheme: string,
    user: string;
    password: string,
    host: string;
    port: number,
    params?: Record<string, any>;
    headers?: Record<string, string>;
};

Edit: I just checked the source code, and parseUri doesn't account for "tel:"-addresses.

I suppose this would be more correct:

export function parseUri(uri: string): {
    family?: string,
    scheme: string,
    user?: string | undefined;
    password?: string | undefined,
    host?: string;
    port?: number;
    number?: string;
    context?: string | null;
    params: Record<string, any>;
    headers?: Record<string, string>;
  };

It's not pretty but I believe it's accurate.

[orgads]

Fixed, thanks for letting me know.