Cannot Use `camunda-bpmn-js` Without Installing `@bpmn-io/form-js`

[philippfromme]

Describe the Bug

I am forced to install @bpmn-io/form-js when using this library due to @bpmn-io/form-variable-provider listing it as a peer dependency and its implementation depending on the getSchemaVariables functionality.

camunda-bpmn-js 🔗 @bpmn-io/form-variable-provider 🔗 @bpmn-io/form-js

Steps to Reproduce

1. Install this library
2. @bpmn-io/form-js dependency must be installed

Expected Behavior

I can use this library without having to install @bpmn-io/form-js. Resolving form variables is optional or the functionality of getSchemaVariables is pulled out of bpmn-io/form-js.

[philippfromme]

@marstamm Are we aware of this?

[marstamm]

This was caused by bpmn-io/form-variable-provider#4. I guess we were to eager to add peer-dependencies. Form-js should be a direct dependency for the variable resolver. I'll create a patch release

[nikku]

I'm not a fan of bundling form-js in the context of BPMN and raised this with the HTO team. Maybe we find a better way to inject the code intelligence, if forms are used (and recognized)?

This would also ensure there exists only a single instance of form-js in the tree.

[marstamm]

I think we are mixing 2 issues here.

1. This Issue: The variable resolver requires a utility from form-js, but declares it as a peer dependency. We do not want to add form-js as direct dependency (or install it manually) for bpmn-js only bundles and still want the code completion ==> mark it as production dependency fix: make form-js a production dependency bpmn-io/form-variable-provider#6

2. The bundle then contains everything from form-js, not just the utility function ==> unrelated to the fist one, should be fixed in form-js

[nikku]

The bundle then contains everything from form-js, not just the utility function ==> unrelated to the fist one, should be fixed in form-js

This is what I reached out to HTO about.

[philippfromme]

I think shipping the utility as a separate library acknowledging the fact that it's used outside of the context of form-js would make sense. This is how we've handled such cases in the past.