Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Installing @thirdweb-dev/contracts in a Pipedream Node.js step fails, which also blocks @thirdweb-dev/sdk. The package authors put the ethers requirement in devDependencies of the SDK package.json, and Pipedream only installs production dependencies, so the import breaks.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Import ethers explicitly above the thirdweb import, for example import { ethers } from "ethers@5", instead of relying on the transitive dependency. A user confirmed this plus the Node 18 runtime upgrade fixed their workflow.
Source: https://github.com/PipedreamHQ/pipedream/issues/5775
Source: https://github.com/PipedreamHQ/pipedream/issues/5775
Shows how to fix cannot install @thirdweb-dev/contracts on a Pipedream Node.js code step. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes this failure: check the file type and size against Safe Attachments detonation limits, confirm the tenant's dynamic delivery setting.
Fixes agent failed to assemble the renewal brief from signed contracts and usage data error failure timeout in the renewal brief agent by applying the specific fix in the steps and proving it on one account first.