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(cofen): fixed error 'URL object could not be cloned.' #127

Merged
merged 1 commit into from
Dec 27, 2023

Conversation

DuCanhGH
Copy link
Owner

@DuCanhGH DuCanhGH commented Dec 27, 2023

Fixes #126.

What?

The issue is as described in the title. This was due to us trying to send the URL object to our worker through postMessage in cacheOnFrontEndNav.

How?

We convert the URL object to a string first.

Copy link

changeset-bot bot commented Dec 27, 2023

🦋 Changeset detected

Latest commit: d9c8f0e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@ducanh2912/next-pwa Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@DuCanhGH DuCanhGH changed the title fix(cache-on-front-end-nav): fixed error 'URL object could not be cloned.' fix(cofen): fixed error 'URL object could not be cloned.' Dec 27, 2023
@DuCanhGH DuCanhGH merged commit a4b8926 into master Dec 27, 2023
5 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.

[Bug - next-pwa]: 'Worker': URL object could not be cloned.
1 participant