Genki Takiuchi

Giving a real example, suppose the edit form of the blog post. We have to avoid to submit without the change. The current blog text is the initial value of...

@fabian-hiller Partially Yes. The dirty state should exist not only for the entire form but for the certain field or fields. For the case of the editing a blog post,...

@fabian-hiller The problem is a bit complicated for making example on the StackBlitz. So I provide a running example that is using the modular-forms with valiForm$ (with my patch applied)...

I have found a workaround. 1. Put a clone hidden field for the field that requires changed value. 2. pipe the `check` to the form schema to confirm they are...

@gioboa Thank you for the answer. I wonder why the change happens to q-manifest.json and chunks even if no updates in my source code. Of course, no dynamic `define` variables...

Ah, I have one more question. Such the piles of small code snippets that are consist of only imports and one export is expected behaviour?. ``` ✓ 1367 modules transformed....

Here is my `vite.config.ts` that causes this issue. ```ts const WIDTHS = [640, 1024]; export default defineConfig(():UserConfig => { return { plugins: [ qwikCity(), qwikVite(), tsconfigPaths(), ], ssr: { external:...

@gioboa Yeah, I think so too. I have tried with no luck. If get success, I will come back :)

Further investigation about the output, I found the cyclic import between `RouterOutlet` and `spaInit` in a chunk maybe regarding to the QwikCity. Chunk: `q-D9K9vuh1.js` ```ts const RouteStateContext = /* @__PURE__...

The why only the larger app cause this issue is maybe those two chunks are not splitted in a smaller apps. To solve this issue, chunks that have circular imports...