We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pr-984
in SDK side:
1- run pnpm dev 2- run pnpm -r exec pnpm link --global --dir ./
pnpm dev
pnpm -r exec pnpm link --global --dir ./
in Wallet side
1- enter in deps.sh file and enable linking with local fuels-ts 2- run pnpm dev:crx
deps.sh
pnpm dev:crx
pnpm build:all
you'll see this error:
this could be related to #765
cc @arboleya
The text was updated successfully, but these errors were encountered:
Maybe related:
Sorry, something went wrong.
@LuizAsFight is this problem still happening?
nope, thanks @Torres-ssf
No branches or pull requests
What version of fuels-ts are you using?
pr-984
Steps to Reproduce
in SDK side:
1- run
pnpm dev
2- run
pnpm -r exec pnpm link --global --dir ./
in Wallet side
1- enter in
deps.sh
file and enable linking with local fuels-ts2- run
pnpm dev:crx
3- run
pnpm build:all
you'll see this error:
![image](https://private-user-images.githubusercontent.com/8636507/241765492-db2765f8-20e5-4be6-9703-10405fef5792.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyODI3MTksIm5iZiI6MTczOTI4MjQxOSwicGF0aCI6Ii84NjM2NTA3LzI0MTc2NTQ5Mi1kYjI3NjVmOC0yMGU1LTRiZTYtOTcwMy0xMDQwNWZlZjU3OTIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMTQwMDE5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTQ4ZWRmZjNhMTNlODljOGNhYTZmNGVlMmFjMzQxMmJlZGY1MGE0NDMyMDM5NzM4OGJkZmY0MDdhOWQ5NjE4NCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.JXzw1SrdJm5shM9oqgTptEPmWDEGumQk4F6sInuKeKM)
this could be related to #765
cc @arboleya
The text was updated successfully, but these errors were encountered: