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

OE-818: Update React, Node, Chakra, and other packages #157

Merged
merged 6 commits into from
Apr 16, 2024

Conversation

jackiequach
Copy link
Collaborator

@jackiequach jackiequach commented Apr 10, 2024

OE-818

Tests for single- and multi- pdf are failing due to DRB being behind the VPN

  • Updates to React 18, Node 20, Chakra 2.8
  • Updates react-pdf to 7.7.1 and the associated pdf-worker files (copied from the pdfjs-dist node_modules as per react-pdf setup instructions)
  • Updates broken Cypress tests
  • Removes @testing-library/react-hooks since it is built into React Testing Library

Copy link

vercel bot commented Apr 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
web-reader ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 16, 2024 3:51pm

Copy link
Member

@kristojorg kristojorg left a comment

Choose a reason for hiding this comment

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

Looks good! Just the one comment about the peer dependencies

package.json Outdated
Comment on lines 37 to 43
"peerDependencies": {
"@chakra-ui/react": "^1.8.7 || 2.x",
"@emotion/react": "^11.8.2",
"@emotion/styled": "^11.8.1",
"react": "^16.8.0 || 17.x || 18.x",
"react-dom": "^16.8.0 || 17.x || 18.x",
"swr": "^2.0.3"
Copy link
Member

Choose a reason for hiding this comment

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

I think these should stay as peer dependencies rather than production dependencies because it allows the dependency to be satisfied by an installing repo having a similar version

Copy link
Collaborator

Choose a reason for hiding this comment

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

I do think we can keep these, but they should be updated to require react 18 and chakra v2. Using chakra v2 in the consuming app while the web reader was on chakra v1 was causing some very strange styling issues.

Copy link
Member

Choose a reason for hiding this comment

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

Oh yes true. The updates were good, just should stay peer instead of production dependencies

@jackiequach jackiequach merged commit 01f5f6d into main Apr 16, 2024
3 checks passed
@jackiequach jackiequach deleted the OE-818/upgrade-react-node-chakra branch April 16, 2024 16:13
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