Build errors in NextJS web app
# helpm
mrr_rosie_63776
09/27/2025, 10:26 PMI keep running into build errors trying to deploy my nextjs app on AWS Amplify. FWIW had similar issues trying to deploy a lambda function calling a BAML function, fixed it by messing around with the packag.json.
Build is fine locally, just failing on staging / prod. Here's a sample of the error:
https://cdn.discordapp.com/attachments/1421624181363314821/1421624181514047609/Screenshot_2025-09-27_at_3.26.53_PM.png?ex=68d9b631&is=68d864b1&hm=b9e7006355674806ef2b1fb06db8a534254ea4db2c80583898010ed1910fe10a&
a
aaronv (BAML)
09/27/2025, 10:27 PMcan you paste your nextjs.config?
aaronv (BAML)
09/27/2025, 10:28 PMyou can try adding this:
Copy code
import { withBaml } from '@boundaryml/baml-nextjs-plugin';
/** @type {import('next').NextConfig} */
const nextConfig = {
webpack: (config, { dev, isServer, webpack, nextRuntime }) => {
.......
return config;
},
};
export default withBaml()(nextConfig);aaronv (BAML)
09/27/2025, 10:33 PMoh one more thing -- what architecture/platform do you deploy onto in amplify?
Is it an amazon linux machine? arm64 or x86? Do you deploy within some docker container, and if so, what image do you use?
m
mrr_rosie_63776
09/27/2025, 10:34 PMa
aaronv (BAML)
09/27/2025, 10:36 PMwhat version is the @boundaryml / baml package in your package.json?
m
mrr_rosie_63776
09/27/2025, 10:37 PM0.207.0
a
aaronv (BAML)
09/27/2025, 10:40 PMhmm lets try simplifying your webpack config block.
Try removing the withBaml(), and just add this directly:
```
const nextConfig = {
serverExternalPackages: ["@boundaryml/baml"],
webpack: (config, { dev, isServer, webpack, nextRuntime }) => {
config.module.rules.push({
test: /\.node$/,
use: [
{
loader: "nextjs-node-loader",
options: {
outputPath: config.output.path,
},
},
],
});
return config;
},
};
export default nextConfig;
aaronv (BAML)
09/27/2025, 10:43 PMand one more thing -- do you use Turbo?
aaronv (BAML)
09/27/2025, 10:43 PMnext build --turbo
m
mrr_rosie_63776
09/27/2025, 10:43 PMyes
a
aaronv (BAML)
09/27/2025, 10:45 PMok one sec we do have a PR open to fix turbo which you can try now as well by copying the code
aaronv (BAML)
09/27/2025, 10:46 PMoh but it seems that in production, it doesn't use turbo right? if you're not sure that's ok
aaronv (BAML)
09/27/2025, 10:46 PMyou can first try the changes above ^^ in production
aaronv (BAML)
09/27/2025, 10:49 PMi can also hop on a call if needed -- how long does it take to deploy AWS Amplify? just curious
m
mrr_rosie_63776
09/27/2025, 10:54 PMi think it worked!!
a
aaronv (BAML)
09/27/2025, 10:59 PMoh snap
aaronv (BAML)
09/27/2025, 10:59 PMdid it??
m
mrr_rosie_63776
09/27/2025, 11:06 PMyes! tysm
a
aaronv (BAML)
09/27/2025, 11:08 PMSweeet, sorry for the snags. Deploying is the hardesr part
aaronv (BAML)
09/27/2025, 11:22 PMif you have issues with turbo this helper function may work, it's just that i think what happened is that you use turbo locally and perhaps amplify isn't, and our withBaml script is bugged and doesnt add that node loader for non-turbo
aaronv (BAML)
09/27/2025, 11:22 PM