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
When creating a Leptos CSR app built by trunk, it is easy to define web workers: One simply creates multiple bin files - one for the actual app, and one for each worker - and one lib file used for interop between them (e.g. using gloo_workers). The distinction between app and workers is defined inside the index.html by trunk-specific attributes. For an example, you might start from here, and replace the app by any Leptos CSR app.
When building a full stack Leptos app we can't use trunk, as cargo-leptos is used instead as build tool. Does cargo-leptos support web workers in a similar way?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When creating a Leptos CSR app built by trunk, it is easy to define web workers: One simply creates multiple bin files - one for the actual app, and one for each worker - and one lib file used for interop between them (e.g. using gloo_workers). The distinction between app and workers is defined inside the
index.html
by trunk-specific attributes. For an example, you might start from here, and replace the app by any Leptos CSR app.When building a full stack Leptos app we can't use trunk, as cargo-leptos is used instead as build tool. Does cargo-leptos support web workers in a similar way?
Beta Was this translation helpful? Give feedback.
All reactions