Yunfei He

`options` get normalized/resolved from rust side, I don't think it could be done easily as you said so.

To be straight, I don't wanna kill your enthusiasm. But so far I don't see a solid reason for accepting the PR.

Notes: - We could map all panics into errors.

I'm not sure it's a bug of Vite. If you just switch these two lines. https://github.com/Artur-/vite-vaadin-problem1/blob/01c59956297768e4642b1f951ff9bd25c75ca52c/frontend/index.ts#L1-L2 And it works. Maybe the cause it's the difference of "import order" between cjs...

My reproduction and the result is the same with @Artur- ``` import '@polymer/iron-list/iron-list.js'; import { Debouncer } from "@polymer/polymer/lib/utils/debounce.js"; import '@vaadin/vaadin-grid-pro/theme/lumo/vaadin-grid-pro-edit-column.js'; import '@vaadin/vaadin-lumo-styles/color.js'; ```

`rolldown:runtime` is like a normal module. There will be only one instance during the build. So if any chunk rely on it, it will imported it from where it exist.

Notes: I readed the thread roughly. I think our orientation should be - If it's possible to provide universal solution that both works on inline and non-inline script, we should...

`strictExecutionOrder` is designed for advanced chunks to ensure correct order on normal modules.

It's not expected. We are working on a fix. And there's a workaround config for you, please pull out module 'rolldown:module' into a standalone chunk using advanced chunks.

> Can you give an elaborate `define arguments`? Do you mean `--a test --a test2`? The post I saw only contains > Just tried using it again, works great except...