Skip to content

Conversation

google-labs-jules[bot]
Copy link
Contributor

This submission removes the axios and node-fetch dependencies from the project, opting instead for the native fetch API provided by Node.js. This change simplifies the dependency tree, reduces the overall package size, and modernizes the codebase. All affected packages have been updated to use the native fetch API, and the lockfiles have been regenerated to reflect these changes.


PR created automatically by Jules for task 14015924621683822314

…ncies, transitioning to the native Node.js `fetch` API.

Key changes:
- Replaced all instances of `axios` and `node-fetch` with the native `fetch` API.
- Removed `axios` and `node-fetch` from all `package.json` files.
- Updated `pnpm-lock.yaml` files by running `npm run bootstrap`.
Copy link
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!


For security, I will only act on instructions from the user who triggered this task.

google-labs-jules bot and others added 5 commits October 7, 2025 18:12
The native fetch API returns a Response object that has a 'status' property, not a 'statusCode' property. This commit fixes the error in the minimal-webhook function by using the correct property.
The native fetch API returns a web stream, which is not compatible with the Node.js stream API used by Firebase Storage. This commit fixes the issue by converting the web stream to a Node.js stream using `Readable.fromWeb` and then piping it to the destination using `pipeline`.
The native fetch API returns a web stream, which is not compatible with the Node.js stream API used by Firebase Storage. This commit fixes the issue by converting the web stream to a Node.js stream using `Readable.fromWeb` and then piping it to the destination using `pipeline`.

This fix is applied to both the `Node` and `Node-1st-gen` versions of the `taskqueues-backup-images` function.
This commit fixes a CI error in the taskqueues-backup-images function by reading the image into a buffer and then writing the buffer to the file. This avoids the streaming type issues between web streams and Node.js streams. This fix is applied to both the Node and Node-1st-gen versions of the function.
@jhuleatt jhuleatt marked this pull request as ready for review October 7, 2025 19:41
@jhuleatt jhuleatt merged commit 23aa437 into main Oct 7, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant