How to test code via npm link or yarn link?

[unphased]

I'm trying to test some changes I made in this repo, and I have engaged yarn link and it's being linked in my project, however there seems to be no entry point, so I'm just getting:

Failed to compile.

./node_modules/drei/index.js
Cannot find module: 'react-three-fiber'. Make sure this package is installed.

You can install this package by running: yarn add react-three-fiber.

I think I'm pretty close to connecting the dots, i see dist/package.json is saying that web.js is the module to load...

[unphased]

OK after manually adjusting the yarn link symlink to point at the dist/ dir, it is working but I'm getting a lot of these types of type errors:

 Types of parameters 'object' and 'object' are incompatible.
            Type 'THREE.Object3D' is not assignable to type 'import("/home/slu/app/client/node_modules/three/src/core/Object3D").Object3D'.
              Types of property 'up' are incompatible.
                Type 'THREE.Vector3' is not assignable to type 'import("/home/slu/app/client/node_modules/three/src/math/Vector3").Vector3'.

This is even after updating my project's three dependency to the same version that the r3f repo is on.

Granted... the host project has barely been tested and i'm surprised it works at all with any yarn commands. So this is very much a frankenstein that I didn't expect to even get as far as I have got.

[drcmda]

this project uses aliasing. just put your test code somewhere in /examples - for instance debug.ts, any change to /src will hot reload

[unphased]

So the "build" (which produces artifacts in dist/) runs fine in r3f repo, I was able to eliminate the three.js type mismatches by matching up three.js version numbers on my app. But I get this "hook called wrong" error out of react now, so I reckon i probably need to match up react versions as well. I think I will just start to surgically replace the built r3f without using the npm link/yarn link approach, though, as that's turning out to be a bit of a headache.

[drcmda]

this is because it ends up resolving multiple react libraries, which won't run. thats why we have to alias react to node-modules. i have never used yarn link, but i can imagine you face these problems there just as you'd face them with aliasing, but at least the latter is fixable: https://github.com/pmndrs/react-three-fiber/blob/master/examples/config-overrides.js#L9-L17

[unphased]

cool. I certainly don't understand how aliasing works, but that's fine. I just went back to a normal setup, and am simply building r3f with yarn, and copying over whatever changed in dist/ into my node-modules. Works a treat!