You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,28 @@ See [Supported Frameworks](Supported_frameworks.md) for details.
77
77
- Non WebAssembly native binaries. Native binaries must be compiled as WASM, which is a more portable and secure format for native binaries.
78
78
- Is this a Docker container?
79
79
- It's similar in the way that you can package and run Node.js code with minimal modifications, but your Browser serves as the operating system instead of a separately managed virtual machine.
80
+
- Can I connect to a server I'm running in WebContainer from an external tool (e.g. Postman) or another website?
81
+
- WebContainer runs in the security sandbox of your browser, which means that if you call an endpoint you created from within your browser you can reach it, but from outside of the browser, it won't. We are working on a way to enable it in the future though: with a toggle switch you'll be able to proxy requests directly into your browser's running webcontainer, similar to ngrok.
82
+
- Which Node.js version can I run?
83
+
- Current version we support is 14.6, other versions will be available as we head into General Availability.
84
+
- Is there a way to install private npm packages?
85
+
- Not yet. While we're in beta we're not enabling private npm registry support (largely for security reasons). We're going to have full private npm registry support once we head into General Availability later this year. We do have private npm registry support available in our enterprise version of stackblitz v1 today though.
86
+
- How can I deploy my app?
87
+
- You can connect your StackBlitz project to a GitHub repository, and use CI workflows to configure such deployment. We are currently looking into integrations with partners such as Vercel, that will allow you to build and deploy to a hosting provider with a single click!
88
+
- Do you support yarn or only npm?
89
+
- We are using Turbo, our own npm client. It's faster, and optimized for running in a browser, and we've designed it to be as similar in use to yarn or npm as possible. So you can run `npm i` or `yarn add` or any other command inside of a StackBlitz V2 project and its calling `turbo` under the hood.
90
+
- Why WebContainers don't run on Safari/iOS/Android?
91
+
- We are ready, but some browsers are still missing features (e.g. SharedArrayBuffer) needed for WebContainers to run. We are super excited to be able to run StackBlitz on mobile devices!
92
+
- Can I connect to any database?
93
+
- We're going to roll out SQLite support in the next few weeks. You'll be able to run it natively in the same WebContainer!
94
+
- Do you support vim or vim mode?
95
+
- It's on our radar, with a prerequisite of enabling full VSC extensions support. We expect to have an announcement about this closer to GA.
96
+
- Can I change the editor keybindings?
97
+
- Soon!
98
+
- Do you support ES modules?
99
+
- Working on it right now!
100
+
- Will you support other languages? Ruby? Python? PHP?
101
+
- The crazy thing is, depending on wasm support for those, it now might be possible. We're expecting some announcements about this over the coming months.
80
102
- How can I help?
81
103
- Check out the [Getting Involved](#getting-involved) section here to see how you can get involved, or [try out WebContainers on StackBlitz.com](https://stackblitz.com/edit/next-starter)
82
104
@@ -88,7 +110,7 @@ The core working group communicates on our Discord and you can get an invite [he
88
110
While many binaries are now available as WASMs, many still need to be converted over. These also tie into the webcontainer-registry for seamlessly swapping out legacy binaries with their corresponding WebAssembly counterparts during installs.
89
111
90
112
## Test compatibility of new toolchains
91
-
It's important for us to identify toolchains that are currently broken to ensure we can track
113
+
It's important for us to identify toolchains that are currently broken so our team can investigate & release runtime compatiblity improvements. Follow our [supported frameworks guide](https://github.com/stackblitz/webcontainer-core/blob/main/Supported_frameworks.md) to help test new frameworks and provide feedback.
92
114
93
115
## Enable live environments for open source projects
0 commit comments