Skip to content
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] - Slider put a NextJS error #4526

Open
coratgerl opened this issue Jan 9, 2025 · 3 comments · May be fixed by #4531
Open

[BUG] - Slider put a NextJS error #4526

coratgerl opened this issue Jan 9, 2025 · 3 comments · May be fixed by #4531
Assignees
Labels
📦 Scope : Components Related to the components 🐛 Type: Bug Something isn't working

Comments

@coratgerl
Copy link

NextUI Version

2.6.11

Describe the bug

When we use a slider we have the following error :

"Accessing element.ref was removed in React 19. ref is now a regular prop. It will be removed from the JSX Element type in a future release."

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

 <Slider
              className="max-w-md"
              formatOptions={{ style: 'percent' }}
              label="Value"
              marks={[
                {
                  value: 0.2,
                  label: '20%',
                },
                {
                  value: 0.5,
                  label: '50%',
                },
                {
                  value: 0.8,
                  label: '80%',
                },
              ]}
              maxValue={1}
              minValue={0}
              showTooltip={true}
              step={0.01}
/>

Expected behavior

Don't have any runtime error

Screenshots or Videos

No response

Operating System Version

macOS

Browser

Chrome

Copy link

linear bot commented Jan 9, 2025

@coratgerl coratgerl changed the title [BUG] - Slider put a NextJS error with React 19 [BUG] - Slider put a NextJS error Jan 9, 2025
@wingkwong
Copy link
Member

please provide your package.json as well

@coratgerl
Copy link
Author

No problem @wingkwong here it is

{
  "name": "app-front",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "next:dev": "next dev --turbo -H 0.0.0.0 --port 3000",
  },
  "dependencies": {
    "@apollo/client": "3.12.4",
    "@emotion/is-prop-valid": "1.3.1",
    "@heroicons/react": "2.2.0",
    "@nextui-org/react": "2.6.11",
    "apollo-upload-client": "18.0.1",
    "clsx": "2.1.1",
    "date-fns": "4.1.0",
    "formik": "2.4.6",
    "next": "15.1.1",
    "next-themes": "0.4.4",
    "notistack": "3.0.1",
    "react": "18.3.1",
    "react-dom": "18.3.1",
    "react-intl": "7.0.4",
    "recharts": "2.15.0",
    "use-debounce": "10.0.4",
    "yup": "1.6.1",
    "autoprefixer": "10.4.20",
    "tailwind-variants": "0.3.0",
    "tailwindcss": "3.4.17",
    "postcss": "8.4.49"
  },
  "devDependencies": {
    "@faker-js/faker": "9.3.0",
    "@graphql-codegen/cli": "5.0.3",
    "@graphql-codegen/typescript": "4.1.2",
    "@graphql-codegen/typescript-operations": "4.4.0",
    "@graphql-codegen/typescript-react-apollo": "4.3.2",
    "@graphql-tools/mock": "9.0.13",
    "@parcel/watcher": "2.5.0",
    "@playwright/test": "1.49.1",
    "@storybook/addon-toolbars": "8.4.7",
    "@storybook/addon-viewport": "8.4.7",
    "@storybook/nextjs": "8.4.7",
    "@storybook/react": "8.4.7",
    "@types/apollo-upload-client": "18.0.0",
    "@types/react": "18.3.12",
    "@types/react-dom": "18.3.1",
    "concurrently": "9.1.2",
    "graphql-middleware": "6.1.35",
    "graphql-request": "6.1.0",
    "lru-cache": "11.0.1",
    "nodemon": "3.1.7",
    "rxjs": "7.8.1",
    "storybook": "8.4.7",
    "typescript": "5.5.2"
  }
}

@wingkwong wingkwong added 🐛 Type: Bug Something isn't working 📦 Scope : Components Related to the components and removed 🔎 Status: More Info Needed labels Jan 10, 2025
@wingkwong wingkwong self-assigned this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 Scope : Components Related to the components 🐛 Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants