What is the Laminar way of restricting access to a certain page?

[IgorWolkov]

Suppose I have a login and a content page, and I don't want to expose the internals of my js app to unauthorised users.
What is the Laminar way of restricting access to a content page? Shall I split the app on login app and content app and route it on a server side?

[raquo]

Yep, you need to split the Scala.js app. Basically you will have two entry points instead of just one, and will create two JS bundles, one with the login page, and another with the rest of the app. And the server needs to serve the HTML file that points to one or the other JS bundle based on the auth cookie or something like that.

…

On Mon., Feb. 19, 2024, 1:26 p.m. Igor Wolkov, ***@***.***> wrote: Suppose I have a login and a content page, and I don't want to expose the internals of my js app to unauthorised users. What is the Laminar way of restricting access to a content page? Shall I split the app on login app and content app and route it on a server side? — Reply to this email directly, view it on GitHub <#153>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAECBMFNASTPOQJ22IOXTQTYUO7QDAVCNFSM6AAAAABDQCQX36VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGI2DCNBWGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[IgorWolkov]

@raquo, thank you very much.