Conversation
…kspace:* Each actor is built on Apify via its own Dockerfile that runs `npm install`. npm doesn't support the workspace: protocol in single-package contexts and fails with EUNSUPPORTEDPROTOCOL when the dep is `workspace:*`. Revert to the pre-migration pattern of `^1.1.4` (the published npm version, which matches the local workspace version). With `linkWorkspacePackages: true` in pnpm-workspace.yaml, local development still gets the workspace symlink; the Apify build sees a real semver range it can resolve from npm. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
B4nan
changed the title
@apify/scraper-tools instead of workspace:*
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.
Summary
After the pnpm migration in #273, each actor's
package.jsonreferenced@apify/scraper-toolsasworkspace:*. The actors are built on Apify via their own Dockerfile (npm install+npm run build), and npm rejects the workspace protocol in a single-package context withEUNSUPPORTEDPROTOCOL. The next manual run ofrelease-generic-actors.yamlwould have failed for every scraper.Reverts the dep specifier on each actor to a regular semver range (
^1.1.4, matching the locally-published version). Becausepnpm-workspace.yamlhaslinkWorkspacePackages: true, local development still resolves to the workspace symlink, but the Apify Docker build now sees a normal range it can install from npm.Verified locally:
packages/actor-scraper/web-scraper/node_modules/@apify/scraper-toolsis a symlink topackages/scraper-tools)npm installagainst the actor'spackage.json(simulating Apify's build) now succeeds — added 410 packages in 24spnpm ci:buildstill passes