Hi @dnprock I think the issue here is the location of the /viz directory. The Netlify deploy is configured to build and deploy functions via Netlify Lambdas, which does not include static files. You can emulate the Netlify build and deploy process locally via this doc. Zip it and Ship it handles the Lambda functions.
I think you’d be best off moving the files from viz/ into web/public. Here’s our document on handling assets and files. However, then you’ll be in a strange situation where the Lamba functions are loading data from your static files deployed on Netlify’s CDN. This might work but, honestly, I’m not sure. You probably don’t need an API for this app, as it seems you could move all the logic in vizjson.js into web/.
(Another idea could be to store them in AWS S3 or other cloud storage. But they are very small files and should be fine to deploy with web/.)
Lastly, because you’re not using a DB (and you might not even use an API), you’ll need to modify the Netlify build and deploy scripts further. (Currently, the scripts will always try to build Prisma DB Connection and fail if they can’t.) Here’s a forum topic with an example for deploying without DB. If you decide to deploy without an API, you’ll just need to update the netlify.toml
to only build the web and not handle functions.
Keep me posted! And let me know if you have any further questions.