themesberg / themesberg/flowbite-react
Warning - Warning: Received `true` for a non-boolean attribute `s`.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 506
- PR merge metrics
- No merged PRs in 30d
Description
- I have searched the Issues to see if this bug has already been reported
- I have tested the latest version
Warning: Received `true` for a non-boolean attribute `s`.
If you want to write it to the DOM, pass a string instead: s="true" or s={value.toString()}.
at a
at li
at NavbarLink (webpack-internal:///(ssr)/./node_modules/flowbite-react/dist/esm/components/Navbar/NavbarLink.mjs:13:23)
at ul
at div
at NavbarCollapse (webpack-internal:///(ssr)/./node_modules/flowbite-react/dist/esm/components/Navbar/NavbarCollapse.mjs:13:27)
at div
at div
at nav
at NavbarComponent (webpack-internal:///(ssr)/./node_modules/flowbite-react/dist/esm/components/Navbar/Navbar.mjs:25:28)
at MegaMenuComponent (webpack-internal:///(ssr)/./node_modules/flowbite-react/dist/esm/components/MegaMenu/MegaMenu.mjs:21:30)
at header
at Header (webpack-internal:///(ssr)/./src/components/Header.js:22:88)
at Lazy
at body
at html
I am using Next.js 14.2.4
Steps to reproduce
- Go to '...'
- Click on '....'
- Scroll down to '....'
Current behavior
Describe what is currently happening and why it's a problem.
Expected behavior
Describe what you expected to happen.
Context
What are you trying to accomplish? Does this only happen on a specific browser, screen size, or operating system?
If possible, provide a live example URL, screenshot, video, or a repository with the minimal reproduction of the issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported SSR stack trace and inspect node_modules/flowbite-react/dist/esm/components/Navbar/NavbarLink.mjs, then check the usage shown at src/components/Header.js. Reproduce the warning with the reported Next.js setup; done when the non-boolean attribute warning is no longer emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100