Because of importing node:xyz packages, the Apify shared packages (e.g. @apify/utilities) and the client require polyfills when bundled in a web application, or used in a non-node server-side runtime. This bloats the bundle size and complicates initial project setup (including Apify Console itself).
All(?) of the used behaviour now has Web API alternatives, which tend to be implemented across all major runtimes and browsers. Swapping the current node imports for the native implementations might solve this issue.
Needs investigation.
Solves #183
Solves #564
Related to apify/apify-shared-js#537
Because of importing
node:xyzpackages, the Apify shared packages (e.g.@apify/utilities) and the client require polyfills when bundled in a web application, or used in a non-node server-side runtime. This bloats the bundle size and complicates initial project setup (including Apify Console itself).All(?) of the used behaviour now has Web API alternatives, which tend to be implemented across all major runtimes and browsers. Swapping the current
nodeimports for the native implementations might solve this issue.Needs investigation.
Solves #183
Solves #564
Related to apify/apify-shared-js#537