Standalone `npm install tinybase` in a new project fails (because of react 19?)

[CodingDoug]

Describe the bug

Following the instructions here:

mkdir MyFirstTinyBaseApp
cd MyFirstTinyBaseApp
npm init -y
npm install tinybase

The above fails during install with:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: myfirsttinybaseapp@1.0.0
npm error Found: react@19.0.0
npm error node_modules/react
npm error   peerOptional react@">= 16.8.0" from electric-sql@0.12.1
npm error   node_modules/electric-sql
npm error     peerOptional electric-sql@"^0.12.1" from tinybase@5.4.8
npm error     node_modules/tinybase
npm error       tinybase@"*" from the root project
npm error   peer react@"*" from @op-engineering/op-sqlite@11.4.7
npm error   node_modules/@op-engineering/op-sqlite
npm error     peerOptional @op-engineering/op-sqlite@">= 2.0.16" from electric-sql@0.12.1
npm error     node_modules/electric-sql
npm error       peerOptional electric-sql@"^0.12.1" from tinybase@5.4.8
npm error       node_modules/tinybase
npm error         tinybase@"*" from the root project
npm error   6 more (react-native, expo-sqlite, expo, @expo/dom-webview, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.2.0" from tinybase@5.4.8
npm error node_modules/tinybase
npm error   tinybase@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error .../.npm/_logs/2025-02-20T21_16_34_699Z-eresolve-report.txt
npm error A complete log of this run can be found in: .../.npm/_logs/2025-02-20T21_16_34_699Z-debug-0.log

However, If I install react 18 first (not the latest 19), I can install tinybase with no trouble:

npm install -D react@18
npm install tinybase

I'm not sure why this is, as I am not very well acquainted with how peer or optional dependencies work.

I discovered this with a similar failure trying to upgrade a multi-module npm workspace (that doesn't use react at all) from tinybase 5.4.7 or 5.4.8. Not sure why this specific upgrade failed today, as I an normally diligent about keeping dependencies up to date.

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

No response

Expected behavior

No response

Screenshots or Videos

No response

Platform

• OS: macOS
• Browser: Not relevant
• Version: 5.4.8

Additional context

No response

[jamesgpearce]

Ouch OK :( did I mess something up?

[jamesgpearce]

Hm, I suspect a dependency that has not marked its React peer dependency as optional, so the latest 19 gets installed. TinyBase v6 beta is going to roll to React 19, so that'll be the best way forward I think... hang in there!

[tnspacetime]

I think that's the problem. I came across the same problem working with React 19 in other contexts. Using --force should solve it.

[jay-zahiri]

+1 for us non-react devs

[gtrias]

I'm also affected by this issue. Having to add --force or --legacy-peer-deps each time I add a new package or perform a npm i is a poor DX.

Can't this issue be fixed from Tinybase codebase?

[gtrias]

I've tried to better understand how this issue can be fixed but even running: "git clone https://github.com/tinyplex/tinybase.git && cd tinybase && npm i" fails for me. :(

Hm, I suspect a dependency that has not marked its React peer dependency as optional, so the latest 19 gets installed. TinyBase v6 beta is going to roll to React 19, so that'll be the best way forward I think... hang in there!

I would be happy to help if there's something I can do :) even if it's just testing

[tnspacetime]

If you want to test here's the link

#220 (reply in thread)

[jamesgpearce]

OK, folks, could you try this on the TinyBase v6 beta?

mkdir MyFirstTinyBaseApp 
cd MyFirstTinyBaseApp
npm init -y
npm install tinybase@beta
ls node_modules 

Going to release this in the next day or two. Thanks!