Skip to content

Conversation

@oiramS
Copy link
Contributor

@oiramS oiramS commented Jan 29, 2026

[PR] fix(deps): ords-remix-jwt-sample dependencies

Description

Updates the following ords-remix-jwt-sample template dependencies:

Package From To
@remix-run/dev 2.16.8 2.17.4
@remix-run/node 2.16.8 2.17.4
@remix-run/react 2.16.8 2.17.4
@remix-run/serve 2.16.8 2.17.4
dotenv ^16.4.5 17.2.3
embla-carousel ^8.2.0 8.6.0
embla-carousel-react ^8.2.0 8.6.0
isbot 4 5.1.34
isomorphic-dompurify ^2.13.0 2.35.0
material-ui-popup-state ^5.3.1 5.3.6
vite 5.4.19 5.4.21
@typescript-eslint/eslint-plugin 7.15.0 8.54.0
@typescript-eslint/parser 7.15.0 8.54.0
eslint 8.57.0 8.57.1
eslint-import-resolver-typescript 3.7.0 4.4.4
eslint-plugin-tailwindcss 3.17.5 3.18.2
esbuild (inherited) 0.27.2 (override)
estree-util-value-to-estree (inherited) 3.5.0 (override)
tar (inherited) 7.5.7 (override)

Regarding the mui-dependencies group dependencies updates (#329): It's not currently possible to update the @mui/material and @mui/icons-material dependencies from 5.16.14 to 7.0.2 since it seems to have introduced a breaking change in the way some of the components get imported and other compatibility issues with the version of remix and react that we are currently using.

Regarding the ords-react-dependencies group dependencies updates (#330), it is not possible to update from react 18.3.1 to 19.1.0 given that the current version of Remix does not fully supports this version of react. There is a Incremental Path to adopt React 19 that we are monitoring closely. The current status of this incremental path is to drop Remix V2 since it's being sunsetted and is currently in maintenance mode and adopt react-router 7 following the Upgrading from Remix Guide. We need to discuss this since dropping Remix has some implications (particularly changing the name of the template and documentation changes).

Fixes # (issue number)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Updated the dependencies listed above in the package.json file of the ords-remix-jwt-sample template.
  • Generated a new project from that template.
  • Executed the dev command of the project and confirmed that there were no import errors.
  • Did a full scan of the project and confirmed that everything worked as expected.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • [N/A] I have made corresponding changes to the documentation
  • My changes generate no new warnings/errors
  • [N/A] I have added tests that prove my fix is effective or that my feature works
  • [N/A] New and existing unit tests pass locally with my changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement. templates-ords-remix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants