stack

Proof of concept for building app with multiple serverless function on vercel

Validate multiple serverless functions and advantages of different technology stacks

Initially, using src/app directory failed, serverless function API proxy and custom directory support was not available.

Therefore, I switched to a structure similar to the rust-runtime demo. and for now, I am testing WebAssembly.

Deploy on Vercel

WASM will not be updated, and the test code has no correlation.

The reason for the directory( /api, /pages/api, /fn ) is to find a way to combine multiple serverless functions, and I am still trying and waiting for more possibilities.

Or

Name		Name	Last commit message	Last commit date
Latest commit History 10 Commits
api		api
pages		pages
public		public
styles		styles
types		types
.eslintrc.json		.eslintrc.json
.gitignore		.gitignore
.prettierrc.json		.prettierrc.json
.vercelignore		.vercelignore
Cargo.lock		Cargo.lock
Cargo.toml		Cargo.toml
LICENSE		LICENSE
README.md		README.md
next.config.js		next.config.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json
vercel.json		vercel.json