You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[TSD-JSDoc] tween.js:15:4 Failed to find parent of doclet 'pc.TweenManager' using memberof 'pc', this is likely due to invalid JSDoc.
[TSD-JSDoc] tween.js:52:4 Failed to find parent of doclet 'pc.Tween' using memberof 'pc', this is likely due to invalid JSDoc.
[TSD-JSDoc] tween.js:681:4 Failed to find parent of doclet 'pc.Application#tween' using memberof 'pc.Application', this is likely due to invalid JSDoc.
[TSD-JSDoc] tween.js:699:4 Failed to find parent of doclet 'pc.Entity#tween' using memberof 'pc.Entity', this is likely due to invalid JSDoc.
/Users/stevenyau/Dev/playcanvas-tween/node_modules/tsd-jsdoc/dist/assert_never.js:5
throw new Error("Unexpected object: " + JSON.stringify(x));
Error: Unexpected object: {"comment":"/**\n * @external \"pc\"\n */","meta":{"filename":"tween.js","lineno":1,"columnno":0,"path":"/Users/stevenyau/Dev/playcanvas-tween","code":{}},"kind":"external","name":"\"pc\"","longname":"external:\"pc\"","scope":"global","___id":"T000002R028308","___s":true}
at Object.assertNever (/Users/stevenyau/Dev/playcanvas-tween/node_modules/tsd-jsdoc/dist/assert_never.js:5:11)
at Emitter._parseTreeNode (/Users/stevenyau/Dev/playcanvas-tween/node_modules/tsd-jsdoc/dist/Emitter.js:196:39)
I understand that the @external tag is not supported, what would be the best way to approach this?
The text was updated successfully, but these errors were encountered:
I'm trying to generate ts definitions for the following library: https://github.com/playcanvas/playcanvas-tween
It is dependent on the PlayCanvas engine as it adds new functionality: https://github.com/playcanvas/engine
So far, I've tried the following:
And the following config:
And get the following error:
I understand that the @external tag is not supported, what would be the best way to approach this?
The text was updated successfully, but these errors were encountered: