Skip to content

changed peerDependencies to support react 17#847

Merged
mattgperry merged 1 commit intomotiondivision:mainfrom
Gerigot:issue-846
Nov 16, 2020
Merged

changed peerDependencies to support react 17#847
mattgperry merged 1 commit intomotiondivision:mainfrom
Gerigot:issue-846

Conversation

@Gerigot
Copy link
Copy Markdown
Contributor

@Gerigot Gerigot commented Nov 16, 2020

As stated in the issue #846 it was impossible to use this library with react 17.

I've modified the peerDependencies to make it work

@codesandbox-ci
Copy link
Copy Markdown

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.

Latest deployment of this branch, based on commit 00ce7f5:

Sandbox Source
Framer Motion: Simple animation Configuration
App Store UI using React and Framer Motion Configuration
Framer Motion: Reorder animation Configuration
Framer Motion: growing item positionTransition issue Configuration
Framer Motion: Image lightbox Configuration

@mattgperry
Copy link
Copy Markdown
Collaborator

Excellent thanks for this

@mattgperry mattgperry merged commit 6b7783a into motiondivision:main Nov 16, 2020
"yarn-deduplicate": "^1.1.1"
},
"dependencies": {
"@emotion/is-prop-valid": "^0.8.2",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@Gerigot
Could you please clarify whether duplicating this from optionalDependencies was necessary?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

this is probably a mistake and should be removed

Copy link
Copy Markdown
Contributor Author

@Gerigot Gerigot Nov 16, 2020

Choose a reason for hiding this comment

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

Oh I see now.
I'm sorry, yes it was a mistake, probably done automatically by my IDE, if it's a problem I'll remove it.

Copy link
Copy Markdown

@o-alexandrov o-alexandrov Nov 16, 2020

Choose a reason for hiding this comment

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

I'm using preact in projects w/ framer-motion and was just passing by :)
Since you probably have a working state w/ React 17, could you please test whether it still installs w/o this dep in dependencies and remove afterwards?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'm an idiot.
I was "fixing" (removing) the dependency and I screw the things up with git. so I've created a new pull request with the fix.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I'm confused. I have a Next.js project that uses React 17. When I do npm i framer-motion I still get the peer dependency error. I thought the problem was fixed? Is there something I need to do to get the latest, fixed version of your library to install? I forced the install with npm i framer-motion --force but was hoping this wouldn't be necessary...thanks!

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I have the same exact problem as Amasa-Delano .

Copy link
Copy Markdown
Contributor Author

@Gerigot Gerigot Nov 27, 2020

Choose a reason for hiding this comment

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

I see that this pull request has been merged in the main branch 11 days ago, but no version of the library has been created since then.
The problem should be that the last version on NPM doesn't have this fix.
You'll have to wait till a version will be created or for now download and build it by yourself.
I'm not the owner of the project, so I don't know if is planned to create a new version and when will that happen.

As a complementary info, if you check the issue #846 is still open and that, I believe, is because there is still no release with this fix, put your comments in the issue, probably is more visible.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

thanks for your quick response and help.

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.

5 participants