Frontend client will always receive 404 errors because of no project_id URL param

[BillyBobFry]

Hey, I noticed an issue when trying to use the frontend client for the first time. When creating a client with createFrontendClient(), the resulting client will always fail to send any valid API requests, and will always receive 404 errors.

This is because it always leaves the project_id part of the URL empty, e.g. it will send GET https://api.pipedream.com/v1/connect//components instead of GET https://api.pipedream.com/v1/connect/my-project-id/components.

It appears that this is because the project ID is being set to the empty string here, in src/wrapper/Pipedream.ts
. Then later on (e.g. here in Client.ts), this empty string is passed to the URL to which the request is made.

I confirmed this by removing clientOpts.projectId = ""; locally and npm linking to my app. The project ID was then present in the URL (although I then received CORS errors).

This is fairly easy to reproduce - create a client with createFrontendClient() and try to send a request.

[jverce]

Hi @BillyBobFry,

Can you provide a code sample where you reproduce this? The reason we set projectId to an empty string is because the token that's use to authenticate API requests in the front-end is essentially a session ID that we use on the back-end to retrieve all the necessary information (including the project ID). The project ID parameter in the API routes/paths is optional, as long as the authentication method allows for it.

We have been testing this via @pipedream/connect-react (which we're migrating to the new SDK version) and haven't seen any 404 errors, but that might be due to some extra setup that we're doing that we haven't properly documented. That's the reason why I'm asking for some sample code that can reproduce the issue.

Thanks!!