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

Update package.json #164

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update package.json #164

wants to merge 1 commit into from

Conversation

L-Qun
Copy link

@L-Qun L-Qun commented Sep 10, 2024

The react peerDependencies version should be greater than 18, as the react peerDependencies version for @mantine/hooks is above 18, and it internally uses useId that does not exist in React 17

image

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@@ -164,7 +164,7 @@
"webpack": "^5.93.0"
},
"peerDependencies": {
"react": ">=17.0.0"
"react": ">=18.0.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I think we want to be react 17 friendly for a short while.

Could you help us identify the hooks that rely on useId and help write a custom impl. that lives within our repo? (@Elvincth is helping us migrate away from @mantine/* so hopefully this shouldn't be a huge issue)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a simpler approach would be to downgrade the version of @mantine/* to meet the requirements of react>=17. What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, that is not an option, it'd require a lot more changes. Mantine v6 -> v7 was a breaking change. 😟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants