chore: move the api surface extractor to its own repo - #4045
Draft
barjin wants to merge 2 commits into
Draft
Conversation
The script is now apify/api-extractor-report, invoked through pnpm dlx, so the crawlee-specific bits it had baked in are passed as arguments.
B4nan
force-pushed
the
chore/extract-api-extractor
branch
from
August 18, 2026 18:15
4c5ba7b to
8fe51f6
Compare
github-actions
Bot
added
the
t-tooling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The extractor now lives in apify/api-extractor-report and is invoked through
pnpm dlx, with the crawlee-specific packages and exclusions passed as arguments.