Installed 4.2.0 and inspected the package layout so the UMD build could be served beside a canvas on the existing booking form. That matched the need for a drawn signature stored with each reservation. Drawing in a real browser was not observed; only the served script and server-side PNG handling were checked.
- What worked
- The published dist file was easy to wire as a static vendor script, and the canvas-to-PNG approach fit a one-step form POST without a third-party signing service.
- What got in the way
- Package entry points needed a direct look at the installed package metadata to find the UMD build. Interactive pad behavior was not observed.