This component has been removed and refactored to be part of the `Page` component exported from `@strapi/strapi/admin`. You should use the `Page` component from there:
```tsx
// Before
import { AnErrorOccurred } from '@strapi/helper-plugin';
// After
import { Page } from '@strapi/strapi/admin';
const MyPage = () => {
// ...
if (error) {
return <Page.Error/>;
}
// ...
};
```
### CheckPagePermissions
This component has been removed and refactored to be part of the `Page` component exported from `@strapi/strapi/admin`. You should use the `Page` component from there:
```tsx
// Before
import { CheckPagePermissions } from '@strapi/helper-plugin';
The behaviour has slightly changed, where previously no permissions would redirect you to the root of the page, now it will render the `NoPermissions` component.
This component has been removed and not replaced. If you feel like you need this component, please open an issue on the Strapi repository to discuss your usecase.
This component aliased `Formik`, something we're working towards removing. The `Form` component and it's sibling exports from `@strapi/strapi/admin` should be used instead:
This component has been removed and refactored to become the `InputRenderer` component exported from `@strapi/strapi/admin`. You should use the `InputRenderer` component from there:
```tsx
// Before
import { GenericInput } from '@strapi/helper-plugin';
// After
import { InputRenderer } from '@strapi/strapi/admin';
```
Note, that the `InputRenderer` component has a different API, and you should refer to the documentation for the `InputRenderer` component.
This component has been removed and refactored to be part of the `Page` component exported from `@strapi/strapi/admin`. You should use the `Page` component from there:
```tsx
// Before
import { LoadingIndicatorPage } from '@strapi/helper-plugin';
This component has been removed and not replaced, you should use the `EmptyStateLayout` component from `@strapi/design-system`.
### NoMedia
This component has been removed and not replaced. If you feel like you need this component, please open an issue on the Strapi repository to discuss your usecase.
This component has been removed and refactored to be part of the `Page` component exported from `@strapi/strapi/admin`. You should use the `Page` component from there:
```tsx
// Before
import { NoPermissions } from '@strapi/helper-plugin';
This component has been removed and not replaced. If you feel like you need this component, please open an issue on the Strapi repository to discuss your usecase. You can easily replicate this in your own project by using the `TextInput` from `@strapi/design-system`:
```tsx
import { TextInput } from '@strapi/design-system';
const MyComponent = (props) => {
return (
<TextInputdisabledplaceholder="No permissions to see this field"type="text"{...props}/>
);
};
```
### ReactSelect
This component has been removed and not replaced. If you feel like you need this component, please open an issue on the Strapi repository to discuss your usecase.
### SettingsPageTitle
This component has been removed and not replaced. If you feel like you need this component, please open an issue on the Strapi repository to discuss your usecase.
### Status
This component should be imported from the `@strapi/design-system` package:
This function has been removed and not replaced. If you feel like you need this function, please open an issue on the Strapi repository to discuss your usecase.
### formatContentTypeData
This function has been removed and not replaced. If you feel like you need this function, please open an issue on the Strapi repository to discuss your usecase.
### useCMEditViewDataManager
This hook has been split into different hooks, each with more ability then it's previous:
This component has been removed and not replaced. If you feel like you need this function, please open an issue on the Strapi repository to discuss your usecase.
### RemoveRoundedButton
This component has been removed and not replaced. If you feel like you need this function, please open an issue on the Strapi repository to discuss your usecase.