Clone of version v0.8.2 but version compatibility problem on installation

[JosueGauthier]

Hello,

EDIT : Clarification of my question

I'm trying to clone the project stable version v0.8.2 to try some potential changes but I'm facing some issues.

In order to install the flume package i do :

git clone https://github.com/chrisjpatty/flume
git checkout v0.8.2
git switch -c mydev

npm install

I have the following errors relating to react and reachid it seems there is a version compatibility issue.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @reach/auto-id@0.10.5
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   dev react@"^18.2.0" from the root project
npm ERR!   peer react@"^18.0.0" from @testing-library/react@14.0.0
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"^14.0.0" from the root project
npm ERR!   2 more (react-dom, react-scripts)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from @reach/auto-id@0.10.5
npm ERR! node_modules/@reach/auto-id
npm ERR!   @reach/auto-id@"^0.10.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0" from @reach/auto-id@0.10.5
npm ERR!   node_modules/@reach/auto-id
npm ERR!     @reach/auto-id@"^0.10.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

So I try an install with the npm install --force command and i got warnings (mostly the same warning as when i run the npm install --save flume via the macket manager).

However when i want to use it as a basis for my development flume not loads correctly.

So i investigate and i try the commands

npm start 
// followed by  
npm test

The problem is that I can't access to the dev server : can’t establish a connection to the server at localhost:3000.

Do you have some ideas about it ? Is there a file somewhere that it explains how to proceed ?

I'm not so familiar with the npm environnement.

Thanks,

[BlueManCZ]

Hello, I noticed this myself too. It looks like npm has a more strict dependency resolution system than yarn has, and a lot of dependencies in both package.json and example/package.json are waaaay too old to even work together correctly in those versions.

And to answer the actual question.

To access localhost:3000, you need to run the local server from the example directory (this one can't even install dependencies with npm install --force, so I'm afraid yarn install is necessary here (for now).

cd example
yarn install
yarn start & npx wait-on http://localhost:3000

Is there a file somewhere that it explains how to proceed?

You can always check the GitHub Actions.