"@prefresh/vite" fails when using "jsxFactory" other than "h" from "preact"

Problem

Emotion users need to be able to use a custom jsxFactory, when using one of the core features of emotion css prop.

When making this change (click to view)

Switching from the suggested:

  esbuild: {
    jsxFactory: `h`,
    jsxFragment: `Fragment`,
    jsxInject: `import { h, Fragment } from "preact";`,
  },

To:

  esbuild: {
    jsxFactory: `jsx`,
    jsxInject: `import { jsx } from "@emotion/react";`,
  },

The "@prefresh/vite" fails with the following error message:

• I’m new to vite, so sorry for not being able to provide you w/ a more useful debug msg

Cannot read property '__e' of undefined

[o-alexandrov]

Btw, as crazy as it sounds, the following addition ended up working. If you add more deps to the exclusion, vite/esbuild stops working properly throwing different errors related to the exports of the pkgs.

  optimizeDeps: {
    exclude: [
      `@prefresh/vite/runtime`,
      `@prefresh/vite/utils`,
    ],
  },

I’ll be closing it, as I don’t have any issues w/ the above.

[itsMapleLeaf]

I see, and the “Cannot read __H of undefined” now shows up when I try to add the exclusions, as mentioned earlier:

	optimizeDeps: {
		exclude: [
			"react",
			"react-dom",
			"preact",
			"preact/compat",
			"preact/hooks",
			"@prefresh/core",
			"@prefresh/vite/runtime",
			"@prefresh/vite/utils",
		],
	},

So it sounds like an issue with Vite that can/should be fixed on their end?

EDIT: After removing this from my config and rerunning the dev server… the error went away 🤔 huh. Curious. There must be some non-determinism at play here