Add transports page to Node.JS docs with info about custom Forge transport

[1999]

This PR is a follow-up of our discussion here: getsentry/sentry-javascript#3669

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sentry/sentry-docs/EarWmYj4ZGk759jAKKvrUreU1L2o
✅ Preview: https://sentry-docs-git-fork-1999-dsorin-forge-custom-transport.sentry.dev

[lobsterkatie]

Hi, @1999. Thanks for working on this project!

I chatted with the team, and we want do to a little structural work before we include third-party integrations. Once we do, it will likely be as a link rather than as a full example, similar to the way we link to community-supported SDKs. The content included in this PR would then be included as part of your README.

(On the topic of your current README, I have one suggestion: You say, "Use it to capture errors and messages from Forge runtime." From reading your transport's code (and given the purpose of transports in general), I'd suggest changing that to, "Use it to send captured errors and messages from Forge runtime.")

I'm sorry - I know you'd talked to Kamil about this already, and he told you to go ahead and make a PR like this one, but we want to start encouraging more folks to contribute transports and integrations, and we decided that including detailed docs about each wasn't going to be scalable. (It also muddies the waters with respect to support responsibility.)

I'm going to close this issue, but please feel free to ping me back with questions.

[1999]

@lobsterkatie that's fair enough, I'm happy with anything you suggest :) I will keep following the issue you mentioned and once this work is done, I'll add a link to our transport there.

I have one suggestion: You say, "Use it to capture errors and messages from Forge runtime." From reading your transport's code (and given the purpose of transports in general), I'd suggest changing that to, "Use it to send captured errors and messages from Forge runtime.")

That's an excellent suggestion. I will do this today.