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.

Sign up for GitHub

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

Jump to bottom

Consider running import/Wasm execution as Worker #125

Open
jacogr opened this issue Jul 5, 2018 · 1 comment
Open

Consider running import/Wasm execution as Worker #125

jacogr opened this issue Jul 5, 2018 · 1 comment
Labels
@client-runtime @client-wasm [enhancement]

Comments

@jacogr
Copy link
Member

jacogr commented Jul 5, 2018

No description provided.

@jacogr
Copy link
Member Author

jacogr commented Jul 6, 2018

The biggest issue I have with this atm is that once we go Worker, the worker (and all dependent files) need to be JS. Until we can find a way around the TS -> JS bridge with workers, I would not like to lose the safety-net provided.

Additionally - with Jest, Workers & logging there are currently issues. If the Worker logs anything to stdout/stderr, it fails under Jest. Early days...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
@client-runtime @client-wasm [enhancement]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacogr