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

Bump react to 17 #14

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

Bump react to 17 #14

wants to merge 1 commit into from

Conversation

avivace
Copy link

@avivace avivace commented Jan 31, 2022

"rimraf": "^3.0.0",
"rollup": "^2.9.1",
"rollup-plugin-peer-deps-external": "^2.2.0"
"rollup-plugin-peer-deps-external": "^2.2.0",
"@wojtekmaj/enzyme-adapter-react-17": "^0.6.6"
Copy link

Choose a reason for hiding this comment

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

this looks like a private fork and package, isn't the official package ready yet? If not, I wouldn't rush with the upgrade

Copy link
Author

@avivace avivace Feb 3, 2022

Choose a reason for hiding this comment

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

this looks like a private fork and package, isn't the official package ready yet? If not, I wouldn't rush with the upgrade

I did a bit of research, an at first glace it looks like they just gave up. The issue for supporting React 17 enzymejs/enzyme#2429 is stuck since almost 2 years now, while the fork we chose here looks seriously maintained and widely adopted (550k weekly downloads, the activity on the repo looks legitimate: https://github.com/wojtekmaj/enzyme-adapter-react-17). At this point the choice is either trust this fork or give up on having enzyme.

Copy link
Member

@ThiefMaster ThiefMaster Feb 3, 2022

Choose a reason for hiding this comment

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

Yes I agree, enzyme feels kind of dead, so unless you want to move to something else altogether for testing I think using the fork is the way to go. We use the same fork in Indico BTW.

@ThiefMaster
Copy link
Member

What's the reason for removing package-lock.json altogether?

@avivace
Copy link
Author

avivace commented Feb 3, 2022

What's the reason for removing package-lock.json altogether?

My bad, I pushed an updated version of it

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.

3 participants