Refactor to dub TypeScript SDK

[steven-tey]

Description

Simplify Dub Raycast Extension by using dub TypeScript SDK.

Also added support for shortening links with custom domains:

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @quuu @jfkisafk @steven-tey you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

We're currently experiencing high demand and limited capacity. As a result, extension reviews might take longer than usual to get the initial review. Please expect an initial review within 5-10 business days.

[jfkisafk]

Hey @steven-tey , I tried to use the sdk too, but got the same error before! So I stuck with axios for now.

[steven-tey]

@peduarte @thomaslombart any ideas here? 👀

[jfkisafk]

We can address these while we try to resolve that Header issue. After that, we might need to see if the DUB error(s) are being properly propagated to the user.

[steven-tey]

@jfkisafk thank you so much! Addressed all your feedback 🙏

[jfkisafk]

Hey @steven-tey this is not a raycast issue, b/c the error is happening during the getAllShortLinks call:

ReferenceError: Headers is not defined
    at Links.list (/Users/stelo/.config/raycast/extensions/dub-link-shortener/search-links.js:22338:26)
    at getAllShortLinks (/Users/stelo/.config/raycast/extensions/dub-link-shortener/search-links.js:23970:20)
    at /Users/stelo/.config/raycast/extensions/dub-link-shortener/search-links.js:216:77
    at /Users/stelo/.config/raycast/extensions/dub-link-shortener/search-links.js:339:11
    at Cr (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:20793)
    at Bn (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:39556)
...

In the generated file, the source code is copied from the dub TS SDK, and the Header is not found here:

https://github.com/dubinc/dub-ts/blob/07f40571e93bc17f0fe0000dc14f625cf18c34cc/src/sdk/links.ts#L81-L83

I think the code that Speakeasy is generating is not adding the import/dependency for Headers correctly.

[steven-tey]

@jfkisafk this should be the Headers Web API which doesn't need to be imported/defined. Is this not supported in Raycast extensions?

[jfkisafk]

It is strange, I can see that the import is not necessary (my IDEs are also indicating that). Not sure why in the generated .js file this is causing an issue @steven-tey . Let me investigate more.

Or easier debugging option would be to just use new Header() in the src .ts code and see if that throws an error.

[jfkisafk]

Hey @steven-tey the problem is exactly this: https://stackoverflow.com/a/65355673

I tested it by just placing:

new Headers({
  "Content-Type": "application/json",
})

in the codepath without the node-fetch import and it failed with Headers not found error at that location. But when I added import {Headers} from "node-fetch", it succeeded. So I think an amendment in the SDK or Speakeasy generation is required to gracefully handle this.

[steven-tey]

@jfkisafk just added a polyfill patch thanks to @disintegrator that fully fixes this! 🤩

CleanShot.2024-07-15.at.08.21.45.mp4

[mil3na]

Is this file necessary?

[jfkisafk]

@steven-tey I had the same question, it looked like a git patch that was already applied. Shall we clean this up?

[mil3na]

Other than this .patch file, things look okay on my side. Ready to merge after I get some answers :)