Eric Bailey

https://github.com/vercel/vercel/blob/main/packages/frameworks/src/frameworks.ts

add `traceId` to all context objects

1

Or look into what's available from various services. This could then be leveraged downstream by stuff like `hypr`.

https://github.com/evanw/node-source-map-support

- https://vercel.com/guides/upgrade-to-zero-configuration - https://vercel.com/docs/runtimes#advanced-usage/advanced-node-js-usage/aws-lambda-api

https://github.com/fabiospampinato/watcher https://github.com/fabiospampinato/atomically#readme

inspo https://github.com/mcollina/on-exit-leak-free/blob/main/.github/workflows/ci.yml#L18

Here's a full dump of what Netlify sends through: ```json { "path": "/api/debug", "headers": { "accept": "*/*", "client-ip": "100.64.0.153", "content-length": "17", "content-type": "application/json", "forwarded": "for=104.153.230.193;proto=https", "host": [ "presta-examples-hybrid.netlify.app" ], "user-agent":...

Attach arbitrary props to build context

2

Could add, say, a CSS-in-JS instance before build, and extract it to a file after all pages have built. This would be configured in `presta.config.js`. That file is currently supported...

The story here is pretty simple: - builds a single lambda to `~//functions/presta.js` — also see #65 - builds static files to `~//static/*` - copies `~/public` to `~//static/*` We should...