monoserve Used AI

some final fixes:
- allowed customizing rolldown's io settings
- started bundling to temporary files in dev instead of base 64 urls, and allowed customizing the location (eg if you made a library external so you need to run functions from the same directory)
- allowed sending back a custom Response, even a streaming one
- improved the dev and (example) prod servers
- worked around a bug where necessary types weren't being bundled
- allowed using (fully typed!) environment variables

one more thing: i made a demo so you can test my monoserver (and feel either the blazing speed or a cold start). i also improved the readme and fixed a few bugs in the typing and in character encoding handling.

made a few minor improvements (allow setting a working directory in the github action, improve docs for consistency+helpfulness) but yeah at this point it works during dev and in prod and i'm completely satisfied

monoserve now works during development. compat with Connect and getting the exports of arbitrary code were hard to get going, but they were interesting and i now know how.

it's working! after fixing a 500 and a cors error (and a hashing typo), it works and it works faster.

i've gotten an initial version of the package going. it's complicated, i need to provide a wrapping function for schema/typing purposes and add a bunch of stubs and emit a bunch of js, but i'm getting there. it's really close to actually working in prod.

monoserve is about using one monoserver that runs all your functions, and we've gotten there already, with an action to deploy, code to serve, and docs to help. it's very fast (see image)! bundling is the next step.