Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Support for monorepos, including lerna or yarn workspaces #196
For my use-case (yarn workspaces) I have been able to work around this issue by using:
[build] command = "npm i firstname.lastname@example.org && yarn && yarn build"
Of course, this is not ideal as it takes additional time to run npm install and yarn install again, however, the cache dir which the npm installed version of yarn uses is the same so it should be all ready for the next time a build is triggered. Bottom line, it has increased building times by about 1 minute for me.
Hopefully, we will be able to revert to the expected behaviour soon, though :)
Btw, thanks for the help @fool
PS. Perhaps it's good practice to call yarn install with
I had a frustrating afternoon playing guess-and-check with netlify builds on my yarn workspaces + lerna repo. I'm 99% sure its todo with netlify's caching scheme for node_modules since my build goes from failing to working if i just clear the cache. I'd don't want to have to do this everytime tho... looking for a config option or ENV var to the effect of
@zanona you can set a build env var
I think why its working for you is actually the
can confirm. I had a good deploy. Then I did a no code change (updated a README). Build failed. Redeployed with the "clear cache" btn and it worked. For now,
Strange. I have a
but i changed my
The issue I'm seeing in my dead builds:
Why do i not have the yarn version i think i should have?
@zanona's workaround solved for now. I added a
[build] command = "npm i -gs yarn && yarn build"
and my pkgJson#scripts:
Any news on this please @fool? In the meantime, please could you update the documentation to make it clear you can only have one
The big thing missing for me is the greater redirect control one gets with the
I don't really even need to share anything, so presumably you could make each site build only aware of a given sub-dir, as if that's the root of the whole thing - then everything else would work as-is?
I’m working on a PR that builds both a static documentation Middleman site and an Ember UI. Part of the script involves checking what branch is being deployed and using a different
But the caching is my concern, it doesn’t seem like it can be hacked around in this manner