Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: repair fetch utility for browser environments #1293

Merged
merged 2 commits into from
Jan 7, 2025
Merged

Conversation

penovicp
Copy link
Collaborator

@penovicp penovicp commented Jan 7, 2025

Motivation and Resolution

tough-cookie, a sub-dependency of fetch-cookie, drops browser support in its latest major release which is required by the latest fetch-cookie minor release, this in turn prevents browser builds that include starknet.js as a dependency from successfully completing.

@penovicp penovicp merged commit 2cb1332 into develop Jan 7, 2025
3 checks passed
@penovicp penovicp deleted the fix/fetch branch January 7, 2025 14:15
@TeddyNotBear
Copy link

TeddyNotBear commented Jan 7, 2025

Hey, could you check your PR so that the patch works correctly in all version please. We've been having a problem with Starknet.JS since this morning with tough-cookie It doesn't seem to work well on ^6.11.0

image

github-actions bot pushed a commit that referenced this pull request Jan 8, 2025
# [6.21.0](v6.20.3...v6.21.0) (2025-01-08)

### Bug Fixes

* correct enum typed data hashing ([#1281](#1281)) ([6e353d3](6e353d3))
* rectify snip-12 violation by removing extra `:` in enum encoding ([#1288](#1288)) ([b903116](b903116))
* repair fetch utility for browser environments ([#1293](#1293)) ([2cb1332](2cb1332))

### Features

* enable base fetch override ([#1279](#1279)) ([0fce61e](0fce61e))
Copy link

github-actions bot commented Jan 8, 2025

🎉 This PR is included in version 6.21.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants