Skip to content

Bump react to 17 - #14

Closed
avivace wants to merge 1 commit into
indico:masterfrom
avivace:patch-1
Closed

avivace wants to merge 1 commit into
indico:masterfrom
avivace:patch-1

Conversation

@avivace

@avivace avivace commented Jan 31, 2022 •

Copy link
Copy Markdown

Comment thread package.json
"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
Copy Markdown

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

@avivace avivace Feb 3, 2022 •

Copy link
Copy Markdown
Author

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.

@ThiefMaster ThiefMaster Feb 3, 2022 •

Copy link
Copy Markdown
Member

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.

@mirekys mirekys Feb 9, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since the fork is now also officially long dead: https://dev.to/wojtekmaj/enzyme-is-dead-now-what-ekl, migration to RTL seems to me like a most viable path to move forward (supports React 16-19): https://testing-library.com/docs/react-testing-library/migrate-from-enzyme/

@ThiefMaster

Copy link
Copy Markdown
Member

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

@avivace

avivace commented Feb 3, 2022

Copy link
Copy Markdown
Author

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

My bad, I pushed an updated version of it

mirekys added a commit to oarepo/invenio-dev-latest that referenced this pull request Feb 6, 2026
* Adds critical blocker documentation for react-overridable v1.2.0 which only supports up to React 17
* Adds ecosystem blocker analysis table showing react-overridable, react-searchkit, and react-invenio-forms dependencies
* Updates migration phase structure: Phase 0 (react-overridable) must be done first before react-searchkit and react-invenio-forms
* Updates target state table to include ecosystem packages with blocker status
* Updates scope to include ecosystem packages as required migration targets
* Updates STOP PROCEED CONDITION to explicitly list all three ecosystem blocks
* Adds react-overridable migration details section with repository, branch, tasks, and verification steps
* Updates execution plan to prioritize ecosystem packages (0-2) before application packages (3+)
* Updates timeline to include Phase -1: Ecosystem Packages Migration (8-11 days)
* Reference PR: indico/react-overridable#14

Co-Authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@mirekys mirekys mentioned this pull request Feb 10, 2026
This was referenced Apr 13, 2026
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.

4 participants