Bump form-data and vtk.js

[dependabot]

Removes form-data. It's no longer used after updating ancestor dependency vtk.js. These dependencies need to be updated together.

Removes form-data

Updates vtk.js from 7.3.2 to 34.6.0

Release notes

Sourced from vtk.js's releases.

v34.6.0

34.6.0 (2025-07-21)

Bug Fixes

• RenderWindowInteractor: sometimes the container maybe null (e750b38)
• VolumeMapper: Fixed accessing property with no valid input (d19e4fe)
• vtkdataarray: fix double allocation when using vtkDataArray.resize (1e5dc5b), closes #3282

Features

• TransformPolyDataFilter: add vtkTransformPolyDataFilter (d5cf3e5)
• TriangleStrip: add vtkTriangleStrip (ccf5ed0)
• vtkCutter: compute cut arrays with vtkCutter (527c2d9)

v34.5.0

34.5.0 (2025-07-08)

Features

• ImageMapper: array-based outline opacity (06b05f9)
• mapper2d: add scalar visibility and scalar color mapping to Mapper2D (d259125)
• polydatamapper2d: cell scalar based coloring for PolyDataMapper2D (bdc7e01)

v34.4.0

34.4.0 (2025-07-07)

Features

• DiskSource: add vtkDiskSource (6c0c3dd)

v34.3.1

34.3.1 (2025-07-01)

Bug Fixes

• CellArrayMapper: correct alpha channel handling to use texture alpha for transparency (e7705e4), closes #3273
• CellArrayMapper: reduces func arguments to improving readability (7b29217)

v34.3.0

34.3.0 (2025-07-01)

Features

... (truncated)

Changelog

Sourced from vtk.js's changelog.

From 33.x to 34

• vtkMapper: many properties have moved to vtkVolumeProperty. The full list of changed methods is: getAnisotropy, getComputeNormalFromOpacity, getFilterMode, getFilterModeAsString, getGlobalIlluminationReach, getIpScalarRange, getIpScalarRangeByReference, getLAOKernelRadius, getLAOKernelSize, getLocalAmbientOcclusion, getPreferSizeOverAccuracy, getVolumetricScatteringBlending, setAnisotropy, setAverageIPScalarRange, setComputeNormalFromOpacity, setFilterMode, setFilterModeToNormalized, setFilterModeToOff, setFilterModeToRaw, setGlobalIlluminationReach, setIpScalarRange, setIpScalarRangeFrom, setLAOKernelRadius, setLAOKernelSize, setLocalAmbientOcclusion, setPreferSizeOverAccuracy, setVolumetricScatteringBlending.
• vtkRenderWindowInteractor: KeyPress, KeyDown and KeyUp events are now observed on the container and no longer on the document. "tabIndex=0" is now automatically added on RWI containers to give focus on your render windows and catch key events. Check the KeyPressEvents example for usage.
• vtkOpenGLTexture: The public create2D* and create3D* methods used to have positional parameters. These methods now use named parameters via passing in an object record.

From 32.x to 33

• vtkColorTransferFunction, vtkMapper: Previous log scaling was disabled but functionality is now quite different from what it maybe was before it was disabled. ColorTransfer function now maps the model.nodes in logarithmic scales so there's an even spacing between powers of ten.

From 31.x to 32

• vtkMapper: remove mapScalarsToTexture from the public API. The function becomes protected and its API changes. This shouldn't cause any issue in most cases.

From 30.x to 31

• Picking: write to depth buffer for translucent pass when picking. This change fixes a picking issue with multiple translucent actors overlaid on top of each other. The hardware selector would just register the propID of the last rendered prop. This was because we explicitly turn off writing to the depth buffer when rendering translucent props as OIT doesn't need it. This change enables writing to the depth buffer when picking in the translucent pass. Applications relying on picked propID would see a difference in the IDs returned by the hardware selector.

From 29.x to 30

• ResliceCursorWidget.interactionEvent: no longer pass an object of {computeFocalPointOffset, canUpdateFocalPoint} but simply the type of the handle that triggers the event (e.g. InteractionMethodsName.RotateLine). The removed values can easily be recomputed by the consumers of the event by checking the type of the handle. Regarding computeFocalPointOffset, it is no longer advised to compute focal point offset for each interaction, instead observing startInteraction() should be considered (see ResliceCursorWidget example).

• ResliceCursorWidget.invokeInternalInteractionEvent(methodName): has been removed and should be replaced by ResliceCursorWidget.invokeInteractionEvent(methodName).

• ResliceCursorWidget.updateCameraPoints(renderer, viewType, resetFocalPoint, keepCenterFocalDistance, computeFocalPointOffset) has lost the keepCenterFocalDistance parameter (because it was ALWAYS the negate of computeFocalPointOffset). The new signature is ResliceCursorWidget.updateCameraPoints(renderer, viewType, resetFocalPoint, keepCenterFocalDistance, computeFocalPointOffset)

• vtkAxesActor: setXAxisColor, setYAxisColor, setZAxisColor now take a single RGBColor (array of 3 numbers) instead of 3 numbers for each color component. The get*AxisColor methods now return an array of 3 numbers instead of an object with r, g, b properties.

From 28.x to 29

• getOpenGLRenderWindow: getOpenGLRenderWindow has been renamed to getApiSpecificRenderWindow in vtkFullScreenRenderWindow, vtkGenericRenderWindow and vtkViewProxy to support WebGL and WebGPU backend. (#2816)
• WidgetManager: Deprecated APIs have been fully removed. (#2910)
• OpenGLRenderWindow: WebXR API has been moved into a WebXR RenderWindowHelper. (#2924)
• DistanceWidget: Removed from vtk.js in favor of vtkLineWidget (#2945)

From 27.x to 28

• vtkManipulator.handleEvent: Change all handleEvent signatures of manipulators. Used to be handleEvent(callData, glRenderWindow): vec3, it is now handleEvent(callData, glRenderWindow): { worldCoords: Nullable<vec3>, worldDirection?: mat3 }.
  • To upgrade: all instances of const coords = manipulator.handleEvent(...) must now be const { worldCoords } = manipulator.handleEvent(...).

From 26.x to 27

• abstractimagemapper: Before this change, the vtkAbstractImageMapper extended vtkAbstractMapper. Now, it extends vtkAbstractMapper3D. Applications with custom sub-classes of vtkAbstractImageMapper that have their own overrides for {set/get}Bounds and {set/get}Center would shadow the superclass methods.

From 25.x to 26

• ResliceCursorWidget: vtkResliceCursorContextRepresentation is deprecated and removed. Instead, a vtkSphereHandleRepresentation is used for rotation and center handles, and a vtkLineHandleRepresenttion is used for the axes. rotateLineInView() now takes an axis name (string, e.g. 'XinY') instead of a substate. enableRotation, enableTranslation and keepOrthogonality in widgetState are replaced by widget behavior accessors (e.g. widgetInView.setEnableRotation(false)). See RCW example.
  • widgetState.setShowCenter() is replaced by widgetState.getCenterHandle.setVisible()
  • widgetState.setSphereRadius() is replaced by widgetState.getCenterHandle().setScale1() and widgetState.getStatesWithLabel('rotation').forEach((handle) => handle.setScale1())

... (truncated)

Commits

• 527c2d9 feat(vtkCutter): compute cut arrays with vtkCutter
• d5cf3e5 feat(TransformPolyDataFilter): add vtkTransformPolyDataFilter
• ccf5ed0 feat(TriangleStrip): add vtkTriangleStrip
• e750b38 fix(RenderWindowInteractor): sometimes the container maybe null
• 1e5dc5b fix(vtkdataarray): fix double allocation when using vtkDataArray.resize
• d19e4fe fix(VolumeMapper): Fixed accessing property with no valid input
• 06b05f9 feat(ImageMapper): array-based outline opacity
• a85aea0 style(mapper2d): removed unused imports, const fixes, lonely-if
• 6c9b986 test(mapper2d): example for scalar coloring with Mapper2D
• bdc7e01 feat(polydatamapper2d): cell scalar based coloring for PolyDataMapper2D
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by floryst, a new releaser for vtk.js since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.