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

Consider releasing lit-labs/ssr with a WASM option #4611

Open
1 task done
bivens-dev opened this issue Apr 6, 2024 · 1 comment
Open
1 task done

Consider releasing lit-labs/ssr with a WASM option #4611

bivens-dev opened this issue Apr 6, 2024 · 1 comment

Comments

@bivens-dev
Copy link

bivens-dev commented Apr 6, 2024

Should this be an RFC?

  • This is not a substantial change

Which package is this a feature request for?

SSR (@lit-labs/ssr)

Description

As things stand currently in order to use @lit-labs/ssr you need to have your web server be a Node application which for a lot of people otherwise wouldn’t make sense.

I was wondering if through standards aligned projects such as this https://github.com/bytecodealliance/javy or this https://github.com/bytecodealliance/ComponentizeJS that it might be possible to build a WASM file as well with SSR support that would allow its usage in non Node backends.

Alternatives and Workarounds

At the moment the only alternative I’m aware is to use an RPC style setup such as gRPC where I run a sidecar style second process but it requires substantial glue code.

@justinfagnani
Copy link
Collaborator

I don't think there's bandwidth on the team to try this right now, but it seems like a lot of it should be trying to run the existing SSR code within one of the JS-in-WASM toolchains. It would be great to see someone try that and report back on if we need to change anything.

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

No branches or pull requests

2 participants