<title>After latest update facing issue with dependency

[hetashah-external]

Prerequisites

• I have searched the existing issues
• I understand that providing a SSCCE example is tremendously useful to the maintainers.
• I have read the documentation
• Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

core

Version

5.x

Current Behavior

In my package.json i am using this
"@rjsf/bootstrap-4": "^5.18.1", "@rjsf/core": "^5.18.1", "@rjsf/material-ui": "^5.18.1", "@rjsf/utils": "^5.18.1", "@rjsf/validator-ajv8": "^5.18.1",

So after latest update when we try to build the application i was facing issue with babel-loader because of the file changes in
@rjsf/core/lib/components/fields/MultiSchemaField.js at some where

onOptionChange = option => { | const { | selectedOption,

Actual error :
Creating an optimized production build... Failed to compile. ./node_modules/@rjsf/core/lib/components/fields/MultiSchemaField.js 101:17 Module parse failed: Unexpected token (101:17) File was processed with these loaders: * ./node_modules/babel-loader/lib/index.js You may need an additional loader to handle the result of these loaders. | * @param option - The new option value being selected | */ > onOptionChange = option => { | const { | selectedOption,

After this error i tried with core version "5.24.3" and now it is working fine but not with "5.24.4" "5.24.7"

Expected Behavior

Currently i am using fixed version "5.24.3" buti want it to download latest version whenever we are running npm install in to the application

Steps To Reproduce

No response

Environment

- OS: Windows
- Node: 18.8.0
- npm:9.8.1

Anything else?

No response

[heath-freenome]

@hetashah-external what are you using to build/run your application? 5.24.4-5.24.8 was updated to provide way better support for ESM builds using vitest. Those changes do not seem to be affecting our vite build. Maybe you just need to update your build system to add support for these updates?

[hetashah-external]

@heath-freenome i am using normal npm install and then creating build using npm run build but when we are installing it is taking new version and that version is giving error at the time of build but when i tried with previous version build is running successful.

[heath-freenome]

@heath-freenome It's possible that the ESM support that was added, in some circumstances is causing breaking change OOTB. Can you see if there is a way to update your webpack configuration to add a different loader that supports ESM for the @rjsf libraries? If not, then I will explore rolling back these changes in a subsequent patch release.