-
Notifications
You must be signed in to change notification settings - Fork 87
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
Error creating publish and functions directories for production build #141
Comments
I've done a bit more digging and here's what I've found
My monorepo directory structure
The 'yarn lerna run build' builds all the libraries in libs and lastly runs yarn build in the Web directory, which runs 'next build' |
hey @MikeM2343! thanks for your patience on this. we're finally getting to work on these greater monorepo issues. we're consolidating everyone's issues into #433, so we'll close this in favor of that. please follow along there, but we'll try to circle back here, too, whenever we release support! 🙏 |
* test: add unit test cases for basePath * test: add integration tests for placing static assets in publish dir (for no basePath and for basePath) * fix: support basepath for static assets
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app builds without any errors
Versions
If you're using file-based installation
**netlify.toml: **
Failed Build file
NetlifyBuild.log
Hello,
I'm not sure I have the correct netlify.toml configuration for the monorepo. I'm pretty sure I shouldn't be specifying a base directory because I need to run a script to build both my libraries and the main app from the root of the repo.
Is there any way to test this locally? I know that when using next-on-netlify, and doing a build, the out_publish and out_functions directories were created on my local system.
Thanks,
Mike
The text was updated successfully, but these errors were encountered: