Breaking Changes ​

Dependency Changes ​

• Formily and Element Plus are both peer dependencies of this component library, so you should install the versions you need yourself. In most cases, compatibility handling is provided across different Element Plus versions, but if Element Plus introduces a major breaking change you may still see rendering issues, in which case you should downgrade.

• Starting from version 2.x, the Vue binding layer moved from @formily/vue to @silver-formily/vue. Pay attention when installing peer dependencies. During usage, components such as Field and SchemaField also need to be imported from @silver-formily/vue. See the official documentation for details.

• Starting from version 3.x, the grid wrapper moved from @formily/grid to @silver-formily/grid. For detailed usage, see the dedicated documentation, and use the built-in createGrid function when creating new Grid instances.

• Starting from version 5.x, every peer dependency used by @silver-formily/element-plus has moved to the independently maintained Silver Formily stack, so the required dependencies are now fully independent from Formily.

Component Refactors ​

Because every component has been refactored, all of them have changed to some extent. They are not listed one by one here, so please refer to the component documentation. If you are migrating an existing project, manually verify the rendering of every form. In particular, the function arguments of FormDrawer and FormDialog have changed and can prevent forms from rendering if not updated.

Component Type Changes ​

from 6.0.0, component prop types use a consistent public component-props model:

• FooProps represents props accepted by consumers; it no longer represents the component constructor type.
• For direct Element Plus wrappers, FooProps includes upstream props, event listeners, and v-model update events.
• Components with Silver Formily extensions add those fields on top of the upstream props, such as options on SelectProps.
• Use FooComponent, such as InputComponent, when you need the component constructor type.
• The old IFooProps names remain temporarily as deprecated compatibility aliases; migrate to FooProps.

import type { InputComponent, InputProps, SelectProps } from '@silver-formily/element-plus'
import { Input } from '@silver-formily/element-plus'

const inputComponent: InputComponent = Input
const inputProps: InputProps = { placeholder: 'Enter a value' }
const selectProps: SelectProps = {
  options: [{ label: 'Option one', value: 'one' }],
}

When creating a custom wrapper with connect, provide its public props as the second type parameter. Runtime attrs, event, and slot forwarding is unchanged. This change primarily fixes cases where upstream component props were inferred as {} in TSX.

Packaging Changes ​

The umd and cjs build outputs have been removed, leaving only esm builds. As frontend tooling evolves, CJS builds should no longer be necessary, though a future UMD build is still possible. The SCSS inside dependencies is also compiled into CSS output so preprocessors are no longer required. The project build system has now fully migrated to Vite instead of the earlier TypeScript-only compilation flow.