will-wow
commented
2 years ago Hi @keilwastaken! Glad you're liking the project, and sorry both that you were having trouble with dependencies, and that I haven't been looking at github issues for it!
Did you ever get this working? It looks like the issues is that a dependency of yours (xraframe-imagetarget) is relying on @types/aframe@0.8.4, and this project declares a peer dependency on @types/aframe@1.0.3. Interestingly, there doesn't seem to have ever been a @types/aframe@0.8.4, or at least NPM doesn't think so: https://www.npmjs.com/package/@types/aframe?activeTab=versions
There was a 0.8.3, but that was three years ago, and the old < 1.0.0 aframes don't really work on current browsers, so the solution may be to get xraframe-imagetarget to incrase their version of @aframe/types.
i was able to download the package by using the --force tag, but wanted to post the issue i had as i think this is a great project and want to see it flurish
xraframe-imagetarget keilaloia$ npm i aframe-typescript-class-components --save npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: xraframe-imagetarget@1.0.0 npm ERR! Found: @types/aframe@0.8.4 npm ERR! node_modules/@types/aframe npm ERR! @types/aframe@"^0.8.3" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @types/aframe@">=1.0.3" from aframe-typescript-class-components@0.3.3 npm ERR! node_modules/aframe-typescript-class-components npm ERR! aframe-typescript-class-components@"*" 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.