Import from `@clientio/rappid-visio` to Angular (11)

Hi!

We’re trying to implement import/export to Visio in our Angular app (v11) Attempt to import anything from @clientio/rappid-visio produces errors shown below. Reproducible with the demo app apps / Chatbot / Angular10 (closest version to ours) if extended with:

// package.json
"@clientio/rappid-visio": "file:rappid/rappid-visio.tgz",

// somewhere in the code
import { VisioArchive } from '@clientio/rappid-visio';
...
// use VisioArchive

Could you give us a hint on how to resolve it, please?

ERROR in ./node_modules/@clientio/rappid-visio/src/formulas/FormulaParser.mjs 5:43-49
Can't import the named export 'Parser' from non EcmaScript module (only default export is available)

ERROR in ./node_modules/@clientio/rappid-visio/src/models/VisioSection.mjs 230:12-13
Can't import the named export 'V' from non EcmaScript module (only default export is available)

ERROR in ./node_modules/@clientio/rappid-visio/src/models/VisioShape.mjs 279:21-22
Can't import the named export 'V' from non EcmaScript module (only default export is available)

ERROR in ./node_modules/@clientio/rappid-visio/src/models/VisioShape.mjs 294:21-22
Can't import the named export 'V' from non EcmaScript module (only default export is available)

ERROR in ./node_modules/@clientio/rappid-visio/src/display/shape.mjs 61:22-23
Can't import the named export 'V' from non EcmaScript module (only default export is available)

ERROR in ./node_modules/@clientio/rappid-visio/src/display/shape.mjs 101:29-30
Can't import the named export 'V' from non EcmaScript module (only default export is available)
....

[kumilingus]

Hi @GeorgiyZhuravlev , you can remove module property from package.json inside of the rappid-visio.tgz for the time being. We need some time to investigate this. Thank you.

[GeorgiyZhuravlev]

I’ll try to find

"skipLibCheck": true in tsconfig.json saved the day 😃

I saw this somewhere in your documentation, but since @clientio/rappid (not visio related) was OK without it, I thought it’s not the case anymore.

Anyway, thank you!