Mikhail Shabarov

**Acceptance Criteria:** 1. Vaadin provides a way to define a JavaScript code in Java, that runs in browser, but added into the frontend bundle, i.e. that is known in advance...

Updated point 4 in the AC to highlight the fact that Vaadin is not going to have a hard-coded predefined list of Vaadin-provided JavaScript. This would be a huge maintenance...

So we have an explicit tomcat version in platform (https://github.com/vaadin/flow/issues/17773#issuecomment-1746720838). Until we can get rid of these (`spring-boot-starter-web` gets a newer versions), let's keep this issue opened.

@ZheSun88 do you have any updates for this?

@steve-todorov no updates unfortunately, this isn't a priority for Vaadin Flow team at the moment. But seems this ticket gets more votes, thus I'm not loosing a hope that we'd...

Reopened, since https://github.com/vaadin/flow/pull/13795 is going to be reverted soon because of several regressions due to serving static resources from context root.

IMO we can try add a default handler when the seconds handler (custom error handler) is not given to `executeJs`. I don't know if it would be possible to switch...

Needs to be reproduced and see what's the original error we have when building with native profile.

Here is a draft branch that has hybrid app with stateful auth - https://github.com/vaadin/flow-hilla-hybrid-example/tree/stateful-auth.

> navigation events and server-side navigation Tested Hilla view -> Flow view navigation and navigation lifecycle events: `BeforeLeaveEvent`, `BeforeEnterEvent `, `AfterNavigationEvent`, including `.addBeforeEnterListener()` listener and `forwardTo/rerouteTo` methods. Works as expected.