Error thrown when used in SparkAR, where cannon.js works

[pmndrs]

Error thrown when used in SparkAR, where cannon.js works

[marcofugaro]

Thanks for the issue! Haven't tried SparkAR myself, could you maybe share a minimal reproducible project with cannon-es? It will help with debugging.
That error is kinda weird, will check if it's something we added in cannon-es.

[marcofugaro]

I've found the issue, you can't use npm modules directly from SparkAR, you have to add them as scripts:

For cannon-es specifically, you have to use the dist/cannon.cjs.js file, and import it as

import * as CANNON from './cannon-es'

I've made an example starter project with cannon-es already installed:

cannon-es_working.arprojpkg.zip

[johannesrave]

Thanks a lot for your quick reply!
I attached a zipped "cannon-es_debuggingProject.arprojpkg", that's the packaged format for SparkAR-Studio projects. If you open it with SparkAR, it'll already do what this issue is about (on my system, anyway). If you want to play around with it, "save as" and it'll extract to a project directory where you point it to. That'll have the "scripts" subdir, where the .ts and the node_modules are etc.

The script is basically blank:

import D from 'Diagnostics';
import CANNON from 'cannon-es';

(async function () {
    D.log("Init cannon-es_Hook");

    const body = new CANNON.Body();
})();

It won't even print the log, as the error is thrown during compilation. With this empty-ish project, the line number is only "856".

I guess finding the (bundled?) JS that SparkAR is trying to compile could help in finding out more. If you yarn add cannon and adjust the import, the log is printed to the SparkAR console. Let me know if you need anything else :)

cannon-es_debuggingProject.zip

[nicolashahn]

@johannesrave did you ever sort this out? Seeing something similar in Studio, though I'm not using cannon.js

[johannesrave]

very cool, thank you @marcofugaro !