Use SDK and indexers package

[PaulRBerg]

Explainer

This PR significantly reduces the maintenance cost of the documentation site by auto-generating:

• The deployment addresses tables from the sablier package, whose source code is available at https://github.com/sablier-labs/sdk
• The indexer APIs tables from the @sablier/indexers package, whose source code is available at https://github.com/sablier-labs/indexers
• The GraphQL documentation using GraphQL Markdown.

In addition, this PR has also made a few other improvements, such as integrating BiomeJS and polishing the ESLint config (using ESLint v9 now).

Issues Closed

• Closes Source deployment addresses from the Sablier deployment package #300
• Closes Use reusable MDX template to DRY-ify the deployment tables #301
• Closes Remove Skale testnet and Berachain Artio #305
• Closes Load benchmarks directly from GitHub repo #311
• Closes Replace Prettier and ESlint setup with Biome #314
• Closes Fix endpoint slug for sepolia #316
• Closes Update the Indexers docs in light of the PRB refactor #323
• Closes Provide Graph API key as "Authorization: Header" in request instead of URL string #324
• Closes Switch order of "References" and "APIs" #328
• Closes Automatically generate GraphQL docs #332

[PaulRBerg]

The PR is now ready for your review @sablier-labs/evm

[smol-ninja]

bun run check is going crazy.

Click to view recording

Screen.Recording.2025-04-30.at.11.26.41.mov

[smol-ninja]

Phenomenal work @PaulRBerg.

[PaulRBerg]

The PR is finally ready for review!!

Not urgent but maybe we can get it done before EthCC — so that we can document the new AVCA product that will be released before or after EthCC.

A review from @smol-ninja and either @razgraf or @gavriliumircea would be helpful (for the Indexers part).

Note: it's a large diff so it's easier to review this by checking out the PR locally and browsing through the new codegens. The areas of interest are:

• cli
• src/autogen/**
• **/graphql/the-graph/**
• **/graphql/envio/**

N.B. you may need to install the latest pre-requisities - check out the install-globals.sh script and the CONTRIBUTING.md file.

[smol-ninja]

Just had a second look and looks good to me now. Just pushed a new commit to fix some warnings and other minor errors.

[PaulRBerg]

Received a question from a user (SYNTHR) for which the docs in this PR would have been helpful:

Specifically, the new section about "Choosing Your Approach":

[razgraf]

This new version auto-generates queries in the API section.

The idea behind the Queries page under Indexers was to provide popular queries stemming from user requests over time. It was a good place to point to for copy-paste examples.

As a general feedback for these auto-generate queries and descriptions: since they can already be found in the indexer's page, in the schema, in the Hasura (or similar explorer) section describing the endpoint, I don't see a point in duplicating them yet again in our docs. They don't provide extra value and they increase maintanance cost since we'll have to remember re-generating if/when we update our endpoints.

I'd propose replacing them with the old custom queries and maybe adding a note about being able to find all filters and field descriptions using Hasura, if there's no human input necessary.

[PaulRBerg]

We can add some default queries, too. But let's please do that after we merge the PR because it's been open for a long time. And let's only add a handful - getting some streams and some campaigns, and that's it.

Also, the Indexers repo provides some default queries now (though they use the $where argument):

https://github.com/sablier-labs/indexers/blob/2e6ed1df82002c1c7141e6eae9e33dbb6c53c363/src/exports/queries/common/streams/graph.ts

I don't see a point in duplicating them yet again in our docs

• It's a much better UX to have the GraphQL docs in the same site where all other Sablier docs are located.
• Readers of the website may be too lazy to open Hasura, or may not like the context-switch.
• Keeping the docs on this site would also make them LLM friendly, and it would enable the Chef AI to provide better answers.

they increase maintanance cost since we'll have to remember re-generating if/when we update our endpoints.

The maintenance cost is super low now, because everything is automated. Bumping the @sablier/indexers package will auto-update the docs.

[razgraf]

And let's only add a handful

The current docs contain the most requested ones e.g. streams from a campaign, campaigns with an asset, recipients who claimed etc. They can be probably be copy-pasted.