Hi @Dennis @luke thanks for getting back, I see how my original post may have been confusing when I mentioned my publish directory was
packages/<my-site>/, I simply included that part because that was a UI label Netlify is displaying (I’m guessing it’s there as a label to make things more user-friendly?)
I have attached screenshots below to illustrate exactly what I’m encountering (after re-linking my github repo, with both deploys w/ cache cleared):
Case 1: NOT WORKING
Deploy failure msg:
Case 2: WORKS (but something is not right)
Notice how in Case 2 where it works, I essentially had to enter the same path for BOTH
base directory as well as part of the
publish directory (so it was essentially
As mentioned in my previous post, I experimented with a few different setups, and noticed that while this issue happens for my current site (that was created before monorepo feature became a thing), using the same settings (from Case 1) for a new Netlify site/project work just fine.
My intuition is that despite this should be working after a github repo re-link, there is probably some cached/old setting somewhere (or because of a particular state that my site/project is in) that is causing the
base directory input to not be prepended correctly during deploy (hence the console output from the failed deploy)
So technically a work around would be to simply delete this project and create a new one and get on with my monorepo happily ever after… but as mentioned in my previous post, that would probably mean 1) I’d have to setup all the domain / contact / etc. settings for the new project and 2) I’d probably loose all Analytics data as well as contact data from the old site, which is less than ideal.
I could also just always include the full path in the
Publish directory input, but that just feels like a hacky workaround…
Let me know if this clears up the issue I’m encountering. For now I’ve basically gone back to my old multi-repo setup until further update.
Again, thanks for looking into this, and happy holidays!