Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal support and going beyond simple testing. #50

Open
frog-o opened this issue Oct 10, 2023 · 2 comments
Open

Terminal support and going beyond simple testing. #50

frog-o opened this issue Oct 10, 2023 · 2 comments

Comments

@frog-o
Copy link

frog-o commented Oct 10, 2023

I been doing a lot of research and I found wasm-webterm very interesting. There are also other wasm terminal but I don't know if they support custom commands. Sadly codesandbox doesn't support this package.

What I wanted to know is will nodebox ever support this terminal or are you just going to keep stuck with basic proto typing?

I tried stackblitz but it is very buggy and doesn't work well in the mobile browser and is not opensource but according to @this post(look at the end of the article)

While unfortunately we are not open-sourcing Nodebox for a variety of reasons, some

Nodebox is not also.

Is there anyway of running this package in codesandbox (or nodeonbox) without relying on microvm( Wich is unbearably slow with an extremely bad interface on mobile)?

@DeMoorJasper
Copy link
Collaborator

Can you create a more detailed repro of what is exactly not working and which bugs you actually encounter?

Our goal with nodebox is to stick with prototyping, in the end full development isn't even possible in the browser without something like microvm's (larger projects usually have complex monorepo setups, databases, ... which a browser cannot run, even if browsers add good FS support which would alleviate some of the current memory issues with in-browser node it would still struggle to support this.)

At Codesandbox we're also investing more in microvm's so our "complete development" will be ran by microvm's, we're aware of the performance issues and working on improving that.

@frog-o
Copy link
Author

frog-o commented Oct 10, 2023

Can you create a more detailed repro of what is exactly not working and which bugs you actually encounter?

I don't really have a error report to give. This is more of a feature request and gladly give more detail. I want to be able to use the wasm-webterm package in a web browser (it is in the node package registry) but it could not be found in the codesandbox ide. I want a way to install it with nodebox. It uses a lot of wasm. If you look at wasm-webterm it talks about to very popular frame work ( Emscripten and WASI) to run apps in the browser.

, in the end full development isn't even possible in the browser without something like microvm.

If I not mistaken This is only partially true ; wasm I believe is changing what the limit of a web browser is allowing for more compiled code in the browser. There are a lot you can do with modern html for example;indexDB and wasm. They even ported the SQL that indexDB uses to wasm to increase proformance. I looking forward to see what Emscripten and WASI
is doing and how there changing the web. The terminal on a web browser is a good example of that and all the wasm that can be run through wasi.

I wanted to look into the code and try to implement something like wasm-webterm (not likely because I bad at programming and you say you aren't opensource) but there's no sense even looking if you are not considering going beyond JavaScript and using some new features of newer browser. I like the fact you trying to support older browser but IMHO it be a shame not to have some features because of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants