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
Browser package (npm) #21
Comments
This is possible and in scope. I have a prototype already and will look into publishing it as a complete work later. |
Note that Qt nextpnr builds are out of scope at the moment. That's an enormous and highly complex dependency that I am not ready to support.
You'd have to also use clang.wasm targeting wasm. That's possible although the simulation speed might not be so great. |
If there's anything I can do to help, I'm happy to contribute. |
Not really, the limiting factor is my time. |
This was discussed on twitter a few times but I thought it would be helpful to track it here.
Use Cases
Why
What's the next best alternative?
Challenges
Accessing files is annoying in the browser. In addition to the wasm file, you also need to deal with the users files, the tech library files. So, ideally those would be packaged in a way that is easy to use.
The text was updated successfully, but these errors were encountered: