Packages are using tsc-compiled files instead of ESM

[sarenji]

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

We're trying to upgrade @rjsf/core, @rjsf/utils and @rjsf/validator-ajv8 from 5.8.2 to 5.14.1. However, we run into a bundle error when importing @rjsf/utils with ESM, because Yarn cannot resolve tslib:

    .yarn/__virtual__/@rjsf-utils-virtual-221548ebb0/0/cache/@rjsf-utils-npm-5.14.1-5c751cec25-68b230fb55.zip/node_modules/@rjsf/utils/lib/schema/getMatchingOption.js:1:23:
      1 │ import { __rest } from "tslib";

Expected Behavior

Ideally we should be able to import @rjsf/utils without error.

I dug into it a little bit and discovered that @rjsf/utils@5.14.1 compiles its files into .js using tsc. The package then sets lib/index.js as the module field., which eventually points to a file that has tslib injected.

On the other hand, version 5.8.2 uses the compiled ESM file instead.

Yarn protects us from ghost dependencies, which is why we get the error.

I believe @rjsf could either:

1. Revert the change to the module field from dist/utils.esm.js to lib/index.js.
2. OR add tslib to the package's dependencies, if you want to continue using TypeScript-compiled files.

Steps To Reproduce

Import @rjsf/utils with Yarn as the package manager.

Example repro: https://codesandbox.io/s/condescending-platform-q8wtk8?file=/src/index.js

Environment

- OS: Mac OS X 13.6
- Node: 18.15.0
- Yarn: 4.0.0-rc.50

Anything else?

No response

[heath-freenome]

@zxbodya Since you made the change to switch to tsc, do you have an idea on how to fix this?

[zxbodya]

good catch, we indeed have incorrect configuration for tsc output -- created a PR updating it