@nbouvrette hello! just wanted to give you an update and let you know that i forked your repo and spent a long time digging through the source to figure out the REAL origin of this error. this filter error is a total red herring that’s a side effect of the actual failure point. the failure exists in/because of the MulLink component, which embedded in its helpers is a function that uses fs.readFileSync for several file manifests in the .next dist. this is not available in the runtime function environment on netlify by default. i’m currently exploring the right solution for you to get only the required files multilingual needs. i’ll update you if/when i have that! lastly, i’ll add that we’re in the middle of a plugin rewrite that i believe would possibly avoid the issue altogether. i’ll be sure to test the rewrite against this project.
Thank you! seems like this was a hard one to troubleshoot. I’ll add this config file for now and please let me know if at some point we don’t need it anymore!
(note: for anyone else who may happen upon this comment – we’re only suggesting the alpha right now to certain users we think it could help. if it’s not suggested directly to you, we don’t recommend trying quite yet. we will be letting everyone know when it’s in beta and free to test out for all!)
Error: The directory “out” does not contain a Next.js production build. Perhaps the build command was not run, or you specified the wrong publish directory. In most cases it should be set to the site’s “.next” directory path, unless you have chosen a custom “distDir” in your Next config. If you are using “next export” then the Essential Next.js plugin should be removed. See Build Plugins | Netlify Docs for details.
Also, I presume the long-term goal would be to have this all within the Web UI?
hello! yes, the long term goal will be for this all to “just work” for users :). my fault again – i didn’t write the instructions and so there are gaps i didn’t realize! please set your publish directory in your netlify.toml (or in the UI) to “.next”.
By the way, can you guys fork my repo to test this? The previous solution is working fine for us so if you think it will be easier to test the new plugin, feel free to use our project as a test app hehe: