Build and functions are different, especially when functions run. I suggest this breakage is not due to the build image itself, but the changing of the default node version used in lambda functions which came into effect a few days ago.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Build Failed After Adding Netlify Lambda Functions | 1 | 1882 | July 22, 2022 | |
Error with netlify-lambda when upgrading it from 1.6.3 to 2.0.x but only when running within a Netlify deploy | 2 | 468 | March 30, 2021 | |
ENOENT problem only on netlify | 8 | 1509 | August 24, 2022 | |
Tyepscript Lambda functions not being found in production | 1 | 376 | August 4, 2020 | |
Deployment issues with Netlify Functions using CRA | 4 | 680 | August 24, 2021 |