Jest 28 with jsdom environment can't parse an exported file from react-colorful

Recently I upgraded jest from v27 to v28 in my app. I noticed that tests that import react-colorful started to fail with the following error message: SyntaxError: Cannot use import statement outside a module.

node: 16.14.0
jest: 28.1.3
jest-environment-jsdom: 28.1.3
react-colorful: 5.5.1

I investigated it a bit and I found a reason. It's happening because jsdom environment can't parse the file. Here is how the conditional exports for react-colorful look like:

react-colorful/package.json

Lines 11 to 19 in e708512

    
           "exports": { 
        
             ".": { 
        
               "browser": "./dist/index.module.js", 
        
               "umd": "./dist/index.umd.js", 
        
               "import": "./dist/index.mjs", 
        
               "require": "./dist/index.js", 
        
               "default": "./dist/index.module.js" 
        
             } 
        
           },

As you can see for the browser you export ./dist/index.module.js that is not CommonJS. If I change it to ./dist/index.js jest is able to handle it.

How to reproduce

package.json

{
  "name": "test-react-colorful",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "test": "jest . --env=jsdom"
  },
  "devDependencies": {
    "@babel/preset-env": "^7.18.10",
    "@babel/preset-typescript": "^7.18.6",
    "@types/jest": "^28.1.6",
    "babel-jest": "^28.1.3",
    "jest": "^28.1.3",
    "jest-environment-jsdom": "^28.1.3"
  },
  "dependencies": {
    "react": "^18.2.0",
    "react-colorful": "^5.5.1"
  }
}

babel.config.js

module.exports = {
  presets: [
    ["@babel/preset-env", { targets: { node: "current" } }],
    "@babel/preset-typescript",
  ],
};

component.ts

import { HexColorPicker } from 'react-colorful';

export const Component = HexColorPicker;

component.test.ts

import { Component } from './component';

describe('Component', () => {
    it('should pass', () => {
        expect(Component).not.toBe(null);
    })
})

I can create a pull request to export CommonJS for browsers if you don't mind

Hi! Thanks for the issue.

AFAIK exporting CJS code for the browser environment is a bad idea and that could break lots of projects using react-colorful.

Browsers can't handle module.exports / require() constructions, so even if it would fixes your issue, it will break the package.

Actually, it's the first time we get an issue with Jest. We use the same approach as Preact does in their bundling and package.json and it always worked well:
https://github.com/preactjs/preact/blob/master/package.json

Hi! Thanks for the reply.

It makes sense. I shouldn't have suggested using CommonJS for browsers.

Everything worked well in Jest 27. I tried downgrading it and the test works fine (even with jsdom environment).

Do you really need to specify export for "browser"? I'm looking at https://github.com/pmndrs/zustand/blob/main/package.json#L23 and I don't see them having a separate export for the browser. Removing it from the package fixes my issue.

I don't insist on any changes in the library. I'm just trying to figure things out.

Hey! I'm facing the same exact issue in a project and I would also recommend removing the "browser" export

There's a pretty good description on @hookform/resolvers on how they dealt with this
The issue react-hook-form/resolvers#396
The pull request react-hook-form/resolvers#435

Hey guys! Thanks for your suggestions!
Makes sense to me: I'll try removing the browser field then.

Just released v5.6.1. Could you please try it in your projects?

Works wonderfully, thanks for the quick change! 🙏🏻

It works for me too. Thanks!

	"exports": {
	".": {
	"browser": "./dist/index.module.js",
	"umd": "./dist/index.umd.js",
	"import": "./dist/index.mjs",
	"require": "./dist/index.js",
	"default": "./dist/index.module.js"
	}
	},