8000 Warp Arbundles is not exported correctly when using Next JS · Issue #707 · permaweb/ao · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Warp Arbundles is not exported correctly when using Next JS #707

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.

Sign up for GitHub

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

Jump to bottom
Closed
LorimerJenkins opened this issue May 14, 2024 · 2 comments
Closed

Warp Arbundles is not exported correctly when using Next JS #707

LorimerJenkins opened this issue May 14, 2024 · 2 comments

Comments

@LorimerJenkins
Copy link

The dependancy warp arbundles of this package does not export correctly, so when trying to use aoconnect as a peer dependancy with Next JS it throws errors and you have to npm patch the package.

The changes that need to be made on the warp arbundles package are:

-var pkg = WarpArBundles.default ? WarpArBundles.default : WarpArBundles;
-var { createData, ArweaveSigner } = pkg;
+let { createData, ArweaveSigner } = WarpArBundles;
@TillaTheHun0
Copy link
Collaborator

Thanks for filing. This sounds like a duplicate of #526 . There is a workaround listed there.

PRs are welcome both here and presumably on warp-arbundles, if it makes it more usable with nextjs

@TillaTheHun0
Copy link
Collaborator

Closing this as a dup. Please comment back if I am mistaken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TillaTheHun0 @LorimerJenkins
0