React-snap fails on deployment with missing chrome dependencies

CORS error in preview env only

Node Express TS source somehow being read as JS

React-snap fails on deployment with missing chrome dependencies

Update: I've resolved to using prerender.io instead for a CDN-based caching solution, this works wonders for my use case. `react-snap` was locally having trouble picking up...

React-snap fails on deployment with missing chrome dependencies

I recently added [react-snap](https://www.npmjs.com/package/react-snap/v/1.16.0) to prerender dynamic content in my React app for SEO and embeds. This, however, breaks the build....

CORS error in preview env only

This is not helpful. I mentioned in the post that I have a working deployment in prod. The title also mentioned the CORS config only fails in preview. This is not an issue of...

CORS error in preview env only

Weird issue here - my preview and prod express apps both have the same code deployed, and I have a corresponding preview and prod frontend fetching from them. CORS is configured by...

Node Express TS source somehow being read as JS

Solved - bit the bullet, migrated to `node16` module resolution and disallowed ts extensions

Node Express TS source somehow being read as JS

Up front i did follow https://vercel.com/guides/using-express-with-vercel to get a working single file express app, it's the relative imports that are problematic here.

Node Express TS source somehow being read as JS

I'm trying to set up a minimal proof of concept of an express TS deployment, with the file structure ``` root - api - index.ts - map.ts - package.json - tsconfig.json etc. ```...