npm i used in networked-aframe is not the same on desktop (i386) versus RPi0 or a Quest (ARM) due to the CPU architecture. Instead one should run the dependencies installation directly on the target platform.
In this specific case it does seem to work, running basic tests, but it is not a good practice.
One could also consider npm i --target_arch=arm --target_platform=linux but supports does not seem perfect. Overall running npm i directly on the target device seems best.
`npm i` used in `networked-aframe` is not the same on desktop (i386) versus RPi0 or a Quest (ARM) due to the CPU architecture. Instead one should run the dependencies installation directly on the target platform.
In this specific case it does seem to work, running basic tests, but it is not a good practice.
One could also consider `npm i --target_arch=arm --target_platform=linux` but supports does not seem perfect. Overall running `npm i` directly on the target device seems best.
utopiah
changed title from npm i is architecture dependant to npm install is architecture dependant2 years ago
utopiah
changed title from npm install is architecture dependant to npm install can be architecture dependant2 years ago
npm iused innetworked-aframeis not the same on desktop (i386) versus RPi0 or a Quest (ARM) due to the CPU architecture. Instead one should run the dependencies installation directly on the target platform.In this specific case it does seem to work, running basic tests, but it is not a good practice.
One could also consider
npm i --target_arch=arm --target_platform=linuxbut supports does not seem perfect. Overall runningnpm idirectly on the target device seems best.npm i is architecture dependantto npm install is architecture dependant 2 years agonpm install is architecture dependantto npm install can be architecture dependant 2 years ago