You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
I've done a bit more digging and here's what I've found
the Netlify deploy was not picking up the @netlify/plugin-nextjs plugin from the toml file in the Web directory as per the structure below
When I added the netlify plugin via the Netlify UI and reran the deploy, I got a different error as indicated in this log: NetlifyBuild2.log
I tried running "netlify build" locally. With debugging, I found that the plugin.onBuild was passed the proper PUBLISH_DIR, and FUNCTIONS_SRC constants (Web\out_publish and Web\out_functions) as per the toml file, but that the publish and functions properties of netlifyConfig had an extra 'Web' directory part in it. i.e. <rootDir>\Web\Web\out_publish. This may not be the case in a web-based deploy, but it does seem to be the case for a local 'netlify build'. The netlifyConfig object also had 'base' set to <rootDir>\Web. I have not set the "base" property of the netlify.toml or in the Netlify Web UI because I need to run the build script from the root directory.
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: