JSDocs got lost during transpilation

[pinussilvestrus]

Describe the Bug

When building the core components (npm run build), the JSDoc comments got lost. As an example, given the Simple component.

/**
 * @param {Object} props
 * @param {Function} props.debounce
 * @param {Boolean} [props.disabled]
 * @param {Object} props.element
 * @param {Function} props.getValue
 * @param {String} props.id
 * @param {Function} [props.onBlur]
 * @param {Function} [props.onFocus]
 * @param {Function} props.setValue
 */
export default function Simple(props) {
  // ...
}

it resolves in weird transpilation changes (imports were places after the comments)

/**
 * @param {Object} props
 * @param {Function} props.debounce
 * @param {Boolean} [props.disabled]
 * @param {Object} props.element
 * @param {Function} props.getValue
 * @param {String} props.id
 * @param {Function} [props.onBlur]
 * @param {Function} [props.onFocus]
 * @param {Function} props.setValue
 */

import { jsx as _jsx } from "preact/jsx-runtime";
export default function Simple(props) {
  // ...
}

Steps to Reproduce

1. Execute npm run build
2. Use one component downstream (example Simple)
3. See that there are no information regarding props anymore (props: any)

Expected Behavior

JSDoc comment stays where they are and can be consumed in downstream projects after transpilation.

An alternative could be to use type linting for that (cf. #65).

Environment

• Host (Browser/Node version), if applicable: Chrome 94
• OS: macOS 11.5
• Library version: 0.4.2

Also related to bpmn-io/bpmn-properties-panel#111 (comment)

[pinussilvestrus]

Maybe related: babel/babel#8507 + babel/babel#8437

[pinussilvestrus]

Moving it to ready because I think that's needed as a minimum to provide proper editor support when using this library.

[nikku]

Moving it to backlog. Let us see how it impacts plug-in development and reconsider the priority on this one then.