Stupid simple FaaS (Function as a Service) runner using GitHub Gists.
- Run JavaScript code from a Gist.
- Run TypeScript transformed code from a Gist.
- Code is executed in a Node.js Worker Thread Pool (tinypool).
- Pretty errors.
FAASADE_CORS_ORIGIN- A comma-separated list of CORS allowed origins. If not set, CORS is disabled (set to wildcard).FAASADE_GIST_ALLOWLIST- A comma-separated list of Gist IDs that are allowed to be run. If not set, all Gists are allowed.
Service functions can be written in JavaScript or TypeScript. The function should be the default export of the file. For JavaScript, the function can be either CommonJS or ES module (ESM is preferred, for CJS use .cjs extension).
/**
* @param {Object} context - The context object.
* @param {Object} context.req - The request object.
* {
* headers: { [key: string]: string },
* method: string,
* url: string,
* body: string
* }
* @returns {Promise<any>} The result of the function.
*/
export default async ({ req }) => {
return 10 % 5;
};Adding Swagger to this project sounds like an overkill, so here's a simple API documentation.
Run the code in the specified file in the Gist.
gistId- [required] The ID of the Gist. You can find it in the URL of the Gist.filename- [required] The name of the specific file in the Gist to run.
Whatever the code in the file returns. If it's a valid JSON, it's gonna be parsed and returned as JSON. If not it's gonna be served as HTML.
- Consider adding support for other languages and runtimes.
- Consider allowing importing http modules (--experimental-network-imports) or Deno.
- Consider adding a simple, Monaco editor-based web interface.
- Consider adding GitHub repo support.
- Consider sandboxing the code execution.
- Add /gist/:gistId route to list all the runnable files in the Gist.
- Add more tests.