-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
chore: migrate away from lerna
#236
Comments
I think would be possible to move to a simpler solution using |
Here are some of the most used tools for monorepo, I think turborepo is a good way https://monorepo.tools/#monorepo-tools |
Hey guys, I started to play with this issue today trying to resolve some of these tasks:
👉🏻 And after some changes I struggle with other issues (that's already solved too):
👌🏻 Until now things are doing very well, all tests are passing... Now we have some new benefits because of the new toolchain: ✅ A very good cache system on the build pipeline (thanks to Turborepo) 🙄 The only thing I'm lit stuck is > fuels-ts@0.0.1 build:example /Users/pedronauck/Projects/fuel/fuels-ts
> pnpm --filter '@fuel-ts/example-contract' build
> @fuel-ts/example-contract@0.6.0 build /Users/pedronauck/Projects/fuel/fuels-ts/packages/example-contract
> exec ./scripts/build.sh
Error occured: Couldn't find fuels. Tried loading: @typechain/fuels, typechain-target-fuels, /Users/pedronauck/Projects/fuel/fuels-ts/packages/example-contract/fuels.
Perhaps you forgot to install @typechain/fuels?
Run with --show-stack-traces to see the full stacktrace
/Users/pedronauck/Projects/fuel/fuels-ts/packages/example-contract:
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL @fuel-ts/example-contract@0.6.0 build: `exec ./scripts/build.sh`
Exit status 1
ELIFECYCLE Command failed with exit code 1. Another thing is that now I have a big PR and maybe this can be an issue too. I'll try to split this into smaller ones! |
Please do ❤️! Big PRs are impossible to review properly. |
lerna/lerna#2703 :(
We should get an alternative
The text was updated successfully, but these errors were encountered: