Ilya Bondarenko

Yes, as I told, when field unmount new form's state calculated and forms global dirty and modified based on list of current registered fields For dirty: https://github.com/final-form/final-form/blob/a95948ab8f2804479b5a6620b88b48525472f0db/src/FinalForm.js#L516-L542 For `modified`, `touched`...

I think for final-form config name should be `keepFormStateOnFieldUnregister` (there is not 'unmount' for fields in final-form) `keepFormStateOnFieldUnmount` will be props for react-final-form (where is fields unmounted)

@aleshanter No 😅 I have no answer about which way to choose for fix, so I did not start with changes. On project I was check initial values and current...

Same problem with `react` and `react-dom` in shared. Config: ``` federation({ name: 'user', filename: 'remoteEntry.js', exposes: { './Profile': './src/Profile.tsx', }, shared: ["react", "react-dom"] }) ```

Hi! For solving `The entry point "react" cannot be marked as external` see my answer in this issue https://github.com/module-federation/vite/issues/16#issuecomment-2072213372 For suppress pre-transform error, try to set `server.preTransformRequests` to `false` in...

Hi all! Just remove `react` plugin usage from vite config. It's solve error, but disable features of this plugin (such as HMR)