valtio not working

[aretrace]

What version of HonoX are you using?

0.1.23

What steps can reproduce the bug?

1. select x-basic template
2. transition app from hono/jsx to @hono/react-renderer
3. install valtio: npm i valtio
4. replace counter island do with valtio counter:

import { proxy, useSnapshot } from "valtio";

const state = proxy({ count: 0 });

export default function Counter() {
  const snap = useSnapshot(state);
  return (
    <div>
      <p>{snap.count}</p>
      <button onClick={() => ++state.count}>Increment</button>
    </div>
  );
}

5. npm run dev

What is the expected behavior?

a basic incremental counter demo rendering and working

What do you see instead?

module is not defined
at eval (/.../node_modules/use-sync-external-store/shim/index.js:8:3)
at instantiateModule (file:///.../node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:53453:11

[vite] Error when evaluating SSR module /node_modules/use-sync-external-store/shim/index.js:
|- ReferenceError: module is not defined

Additional information

valtio: https://valtio.pmnd.rs

valtio-signal seems to be working, jotai test counter also works

[dai-shi]

Valtio v2 may help: npm i valtio@next

[aretrace]

Using Valtio v2:

• hono/jsx
  • basic counter component using state object from external file: not working
• hono/jsx && @hono/react-compat
  • basic counter component using state object from external file: working
  • straightforward async using fetch in state object from external file: not working
    • using Suspense
• @hono/react-renderer
  • basic counter component using state object from external file: working with warnings
  • straightforward async using fetch in state object from external file: not working
    • using Suspense

I encourage testing for each package combinatorial use case as errors differ in most individual cases of a particular mix.

[ElasticBottle]

Did anyone ever get a workaround for this? Running into a similar issue with valtio and bcryptjs

[aretrace]

hono implements its own internal react-like library, so best workaround is to just use vanilla react 🤷