Vite + Preact: useState returns true on first call

Reproduction

Link to example: https://github.com/LXSMNSYC/scoped-model/tree/master/examples/preact-scoped-model

Sandbox: https://codesandbox.io/s/musing-spence-45g0y

  console.log('First call', useState(0));
  const [count, setCount] = useState(initialCount ?? 0);
  console.log('Next call', useState(0));

  const increment = useCallback(() => {
    setCount((c) => {
      console.log('Current State', c);
      return c + 1;
    });
  }, []);

  const decrement = useCallback(() => {
    setCount((c) => {
      console.log('Current State', c);
      return c - 1;
    });
  }, []);

Steps to reproduce

1. run yarn at the root.
2. run yarn dev.
3. See console logs (should output “true” on First calls).

Expected Behavior

1. Should have similar output with ‘Next Call’ logs.
2. setState should be able to receive the current state.

Actual Behavior

1. Initial call for a useState returns ‘true’ instead of the state and the setState function.

1. adding a set state action function as a parameter for a setState call receives an undefined state.

Additional info

• preact@^10.4.8
• vite@^1.0.0-rc.4

[JoviDeCroock]

I don’t think this is our fault, it works in other bundlers. Essentially we could implement something that prevents double injection but the code is still included duplicated which is never a good thing.

We are relying on default resolution behaviour where it deduplicates.

A reason for this error however could be a lot of mixed imports within this lib code itself and the bundler used to produce the dist.

Maybe scoped-model should limit itself to only Preact and Preact/hooks imports for a Preact specific version?

[lxsmnsyc]

Thanks for the response @JoviDeCroock.

I’ll close this for now. I’ll be trying out other JS bundlers and see if the problem still persists.