The Quickstart guide for external tasks (https://docs.operaton.org/docs/get-started/quick-start/service-task) contains a JavaScript dependency for operaton-external-task-client-js which is a package that does not currently exist on npm. There is a package called camunda-external-task-client that seems to be the one intended here given that Operaton is a Camunda fork and it provides the same exports.
Either the package needs to be forked to make the install work under the given name or the code needs to be refactored to reference the externally provided package.
I'm not qualified to suggest either as better or may not see all options. In my opinion it sadly makes an avoidable bad first impression if the first real code example already has dependency issues.
The Quickstart guide for external tasks (https://docs.operaton.org/docs/get-started/quick-start/service-task) contains a JavaScript dependency for
operaton-external-task-client-jswhich is a package that does not currently exist on npm. There is a package calledcamunda-external-task-clientthat seems to be the one intended here given that Operaton is a Camunda fork and it provides the same exports.Either the package needs to be forked to make the install work under the given name or the code needs to be refactored to reference the externally provided package.
I'm not qualified to suggest either as better or may not see all options. In my opinion it sadly makes an avoidable bad first impression if the first real code example already has dependency issues.