-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. #505
Comments
Hello @eng-ahmad-sameer Does this occur without the user prop ? Looking at the source code of the error, it seems that its related to an incorrect ressource icon, could you maybe check if you are passing a correct name for your resources icons ? |
|
This my next admin props: ’’’ My main layout props: const mainLayoutProps = getMainLayoutProps({ |
Does this occur on a custom page or all pages ? |
All pages. It happens if the user prop added to NextAdmin or MainLayout component |
Ah looks like its because of an issue with the heroicons version. Could you add the following resolution in your package.json and re-install ?
|
@foyarash |
This is fixed in 7.1.1 |
Description
An error happened when passing the "user" props in the
NextAdmin
component.Reproduction URL
n/a
Reproduction steps
Next router
App router
Next Admin version
^7.1.0
Screenshots
No response
Next Admin options
No response
Logs
Browsers
Chrome
The text was updated successfully, but these errors were encountered: