Skip to content

Commit 6113e26

Browse files
authored
Merge branch 'main' into patch-1
2 parents c4fc5e0 + abb20dd commit 6113e26

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The initial focus for the applications of WebContainer will be Node.js based dev
1616

1717
While containerization solutions like Docker and VMs have improved environment portability, they still leave much to be desired in terms of speed, security, consistency, and accessibility. A full operating system is brought along (and ideally secured and hardened) with each virtual instance, and system resources are difficult to efficiently share between containers. Operating systems and browsers have a lot in common. They're both [user agents](https://en.wikipedia.org/wiki/User_agent) that run multi-tenant environments containing arbitrary (and possibly insecure) code. The browser provides a better primitive for a modern operating system, being networked, secure, and multi-tenant by default.
1818

19-
The advent of WebAssembly has introduced an opportunity to fix these problems in a fundamentally new way. Initiatives like WASI have paved the way for a new type of operating system interface. But to date, nearly all software development continues to be done with local binaries. Other initiatives focus on lower level APIs that are required for this change. This is important work, but the feedback loop is impaired without developers being able 'dogfood' their normal development toolchains on top of these APIs.
19+
The advent of WebAssembly has introduced an opportunity to fix these problems in a fundamentally new way. Initiatives like WASI have paved the way for a new type of operating system interface. But to date, nearly all software development continues to be done with local binaries. Other initiatives focus on lower level APIs that are required for this change. This is important work, but the feedback loop is impaired without developers being able to 'dogfood' their normal development toolchains on top of these APIs.
2020

2121
# Key goals
2222

Supported_frameworks.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,11 @@
22

33
The following is a list of frameworks that we have actively tested and are supported. Other frameworks may work out of the box. If not, feel free to open an issue on this repo.
44

5-
- [Next.js](https://stackblitz.com/fork/nextjs)
5+
- ExpressJS ([simple](https://stackblitz.com/edit/node-dmbz1u) / [advanced](https://stackblitz.com/edit/expressjs))
6+
- [Koa](https://stackblitz.com/edit/koa-starter)
67
- [NestJS](https://stackblitz.com/fork/nestjs-starter)
7-
- [ExpressJS](https://stackblitz.com/edit/node-dmbz1u)
8+
- [Next.js](https://stackblitz.com/fork/nextjs)
9+
- [Nuxt](https://stackblitz.com/github/nuxt/starter/tree/stackblitz)
810

911
## Add support for a framework
1012

0 commit comments

Comments
 (0)