Using react-three/fiber and react-three/drei as dependencies in an NPM package

[ashleymvanduzer]

Just wondering if anyone has any experience doing this? I am building a package that will render a canvas with a few components inside, namely components composed with gltfjsx wrapped in suspense. I am running into all types of issues. If anyone could shed any light on this topic it would be greatly appreciated!

[joshuaellis]

What kind of issues? Is there a reason you need to bundle these libraries? Couldn't they be peer-deps?

[ashleymvanduzer]

@joshuaellis Thanks for getting back to me. The company I am working for would prefer if they were dependencies, i guess as to not bloat the package json any more than it needs to be, though I would imagine in either case it's just about the same. To be clear this is my first time making a package so it's probably just my inexperience. The issue I am running into at the moment is that classic could not load model in json at position 0, which means I have my models in the wrong place. They were in a public folder but I moved them to src, updated the import route but am still getting the same error. I am also getting an error below that that says the above error occured in the forwardref component, though that was happening even before I could explicitly see the json at position 0 error, which made me think it was an issue with canvas initially, but maybe the error was just not being output to the console at that point.

Honestly I feel like they should be peer dependencies along with three, my logic being that a package has a recommended bundle size that three sends skyrocketing. Would having them as peerDeps be more reliable/less bug prone?

[ashleymvanduzer]

I just took out all the components loading glbs and loaded a plane from drei. The plane works great (😭 😂 ) and I am thrilled to know there is nothing fundamentally wrong with how I set up the package. So yeah, the issue is just my inexperience building packages.