Error: Cannot find module 'lib' in require stack... about camunda-8-js-sdk HOT 5 CLOSED

Thanks for reporting this. I know that alpha.3 had this issue. Let me reproduce it with alpha.4

from camunda-8-js-sdk.

This is due to the way that the package is structured in TypeScript, see here: #110

Two things: first of all, to solve this, I am taking out the module mapping and using explicit relative paths in the source, to avoid complicated transpilation configuration.

Secondly: all the tests in CI are running using ts-jest, which means they prove the code before it is transpiled. To address this, and make sure that transpilation and packaging issues which are not caught by the current test suite don't get through, I am adding to the CI testing an npm build step followed by a test run using the transpiled code in dist and the package.json entry point. This simulates as close as possible the code that will be installed by npm i when the package is installed, and will catch issues of this class this before they hit NPM.

This will be done in the next 24 hours.

from camunda-8-js-sdk.

I've released alpha.5 which addresses this.

Now, I will write the tests to make sure that we catch issues of this class before a package gets released.

from camunda-8-js-sdk.

alpha.6 includes the smoke test step, and also fixes an issue where instantiating a Camunda8 object with OAuth disabled would throw an error.

from camunda-8-js-sdk.

Thanks for you work !

from camunda-8-js-sdk.