feat(Build): modernize build and test tooling with Vite/Vitest & oxlint/oxfmt by daker · Pull Request #3435 · Kitware/vtk-js

daker · 2026-03-03T12:23:10Z

Context

This PR completes a tooling migration from the legacy webpack/rollup + Karma/Tape setup to a unified Vite + Vitest stack. It updates local development, build output, test execution, and CI integration to run on the new toolchain.

Results

Reduce maintenance overhead from multiple legacy build/test systems.
Standardize on a modern, faster toolchain for both local and CI workflows.
Improve consistency between build and test environments by sharing Vite-based config.
Remove UMD build.
Everything should works as before.

Changes

Replaced legacy build configuration with vite.config.js.
Added Vitest browser-runner configuration via vitest.config.js.
Migrated test infrastructure and tests to Vitest.
Removed old webpack, rollup-legacy, and Karma-related configs/plugins/utilities.
Migrate ExampleRunner to vite devserver.
Updated GitHub Actions workflows to run the Vite/Vitest pipeline.
Updated dependencies and lockfile to reflect the new build/test stack.
Documentation and TypeScript definitions were updated to match those changes

PR and Code Checklist

semantic-release commit messages
Run npm run reformat to have correctly formatted code

Testing

This change adds or fixes unit tests
Tested environment:
- vtk.js:
- OS:
- Browser:

finetjul

J'ai tout review sauf package-lock.json

LGTM

Utilities/ExampleRunner/example-runner-cli.js

Sources/Rendering/Core/HardwareSelector/test/testHardwareSelectorSpeed.js

jourdain · 2026-03-10T23:54:36Z

Utilities/rollup/plugins.js

+  return {
+    name: 'vtk-serve-data',
+    configureServer(server) {
+      server.middlewares.use('/Data', (req, res, next) => {


I think we serve /data lower case rather that /Data

Remember, you had to fix that for the website / examples online.

jourdain · 2026-03-10T23:58:08Z

package.json

@@ -27,13 +27,12 @@
    "url": "https://github.com/kitware/vtk-js/issues"
  },
  "homepage": "https://github.com/kitware/vtk-js#readme",
-  "main": "./dist/umd/vtk.js",


can't Vite also generate a umd format too? It can be ok to discontinue umd but we need to let the community know. I think you've updated the doc to promote esm usage as script.

Maybe that is enough. What do you think @finetjul ?

Projects that are still using the UMD package :

https://github.com/openUC2/ImSwitch
https://github.com/sandialabs/slycat

I do not realize how much work it is to keep umd builds. If it is challenging, ok to drop it.
If we drop umd, the PR should be considered as a breaking change (new major) and documented (in BREAKING_CHANGES.md how to move from umd to esm).

jourdain · 2026-03-11T00:06:47Z

LGTM, @finetjul I let you merge it. I put some comments as I did not tested.

jourdain · 2026-03-25T18:28:35Z

Should we try to rebase? What is preventing us to merge that PR?

jourdain · 2026-03-25T18:29:14Z

@PaulHax @finetjul @sankhesh

daker · 2026-03-25T18:34:57Z

@jourdain i can try to bring back the umd build with vite but we need to test the builds to see if nothing is broken.

jourdain · 2026-03-25T18:41:13Z

@finetjul would you be able to test the build?

finetjul · 2026-03-25T19:28:26Z

@finetjul would you be able to test the build?

not before next week

PaulHax

npm run docs:build-examples fails because Rollup packages removed from package.json but still imported in build-examples.mjs

UMD bundle still works, thanks for that.

PaulHax · 2026-04-10T14:45:10Z

Sources/Rendering/Misc/GenericRenderWindow/test/testGenericRenderWindowCreateDelete.js

      setTimeout(createRW, 100);
    } else {
      popMonitorGLContextCount();
      Promise.all(images).then(gc.releaseResources);


Suggested change

return Promise.all(images).then(gc.releaseResources);

We need to wait for these promises to finish before ending the test.

PaulHax · 2026-04-10T15:39:59Z

Utilities/ExampleRunner/example-runner-cli.js

+  'vite.example.config.mjs'
+);
+const DEFAULT_HOST = '0.0.0.0';
+const DEFAULT_PORT = '9999';


Looks like we changed the docs in the PR to say examples are on 3000, but I think this will carry through and make the example port 9999

PaulHax · 2026-04-10T16:01:58Z

vite.config.js

+      outDir: umdOutputDir,
+      emptyOutDir: true,
+      sourcemap: true,
+      cssCodeSplit: false,


We should probaly note in BREAKING_CHANGES.md that UMD users will need to add <link rel="stylesheet" href="vtk.js.css"> now cuz CSS is not injected into JS bundle.

Or we could not break things by adding a plugin to bundle CSS in UMD.

daker force-pushed the vite-vitest-migration branch 29 times, most recently from 65d7ab0 to 825c998 Compare March 5, 2026 12:40

daker marked this pull request as ready for review March 5, 2026 12:51

finetjul reviewed Mar 10, 2026

View reviewed changes

Utilities/ExampleRunner/example-runner-cli.js Outdated Show resolved Hide resolved

Sources/Rendering/Core/HardwareSelector/test/testHardwareSelectorSpeed.js Show resolved Hide resolved

daker force-pushed the vite-vitest-migration branch 5 times, most recently from dfa94d2 to a9bdd89 Compare March 10, 2026 23:04

jourdain reviewed Mar 10, 2026

View reviewed changes

daker mentioned this pull request Mar 25, 2026

fix(Testing): match webpack define name to JS global for VTKJS_TEST_PATTERN #3451

Merged

daker added 5 commits March 25, 2026 20:24

feat(build): migrate to vite

a9a683d

feat(build): migrate to vitest

731a45f

feat(Example): switch example runner to Vite devserver

856c265

fix(RenderWindowInteractor): migrate testChordedButtons to vitest

f867c2a

feat(build): migrate to oxlint/oxfmt

8a85370

daker added 2 commits March 25, 2026 20:28

feat(build): bring back to vitest comments

588c162

feat(build): bring back to umd build

11d0f37

daker force-pushed the vite-vitest-migration branch from f651a58 to 68d34ac Compare March 25, 2026 19:34

docs(TriangleStrip): migrate testTriangleStrip to vitest

ed7c3c4

daker force-pushed the vite-vitest-migration branch 2 times, most recently from 6f5a9ab to 39c691d Compare March 25, 2026 19:49

docs(ClipPolyData): migrate testClipPolyData to vitest

7aa3181

daker force-pushed the vite-vitest-migration branch from 39c691d to 7aa3181 Compare March 25, 2026 19:56

docs(TriangleStrip): fix testTriangleStrip

0c570c0

PaulHax reviewed Apr 10, 2026

View reviewed changes

Uh oh!

Conversation

daker commented Mar 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Context

Results

Changes

PR and Code Checklist

Testing

Uh oh!

finetjul left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jourdain commented Mar 11, 2026

Uh oh!

jourdain commented Mar 25, 2026

Uh oh!

jourdain commented Mar 25, 2026

Uh oh!

daker commented Mar 25, 2026

Uh oh!

jourdain commented Mar 25, 2026

Uh oh!

finetjul commented Mar 25, 2026

Uh oh!

PaulHax left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

daker commented Mar 3, 2026 •

edited

Loading