chore: HNT-1044-dependency updates #1256
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Upgraded webpack, dev server, and test infrastructure to address compatibility issues. Webpack configuration: - Updated webpack-dev-server to v5 with complete API migration - Migrated to new setupMiddlewares pattern from deprecated before/after hooks - Updated static file serving configuration (contentBase → static) - Fixed splitChunks configuration for webpack 5 compatibility - Removed deprecated options (futureEmitAssets, requireEnsure parser) - Updated PostCSS loader to use postcssOptions - Fixed TerserPlugin configuration for webpack 5 Node.js polyfills: - Added browser polyfills for process, Buffer, crypto, stream, and url - Configured webpack ProvidePlugin for global availability - Added TypeScript declarations for polyfilled globals Jest updates: - Migrated to Jest v30 with updated transformer API - Updated file and CSS transformers to return code objects - Fixed test matchers (toBeCalled → toHaveBeenCalled) - Added jest-environment-jsdom for Jest 28+ compatibility - Removed deprecated testRunner configuration Dev server: - Configured port 3000 as default - Updated client configuration for WebSocket connections - Migrated to new middleware registration pattern
mmiermans
reviewed
Oct 6, 2025
Contributor
mmiermans
left a comment
mmiermans
left a comment
There was a problem hiding this comment.
Nice work! npm run build runs successfully for me locally.
Could you try to avoid the need for as any? It may hide type compatibility issues.
jwalterss
added a commit
that referenced
this pull request
Oct 8, 2025
* chore: update build dependencies and tooling Upgraded webpack, dev server, and test infrastructure to address compatibility issues. Webpack configuration: - Updated webpack-dev-server to v5 with complete API migration - Migrated to new setupMiddlewares pattern from deprecated before/after hooks - Updated static file serving configuration (contentBase → static) - Fixed splitChunks configuration for webpack 5 compatibility - Removed deprecated options (futureEmitAssets, requireEnsure parser) - Updated PostCSS loader to use postcssOptions - Fixed TerserPlugin configuration for webpack 5 Node.js polyfills: - Added browser polyfills for process, Buffer, crypto, stream, and url - Configured webpack ProvidePlugin for global availability - Added TypeScript declarations for polyfilled globals Jest updates: - Migrated to Jest v30 with updated transformer API - Updated file and CSS transformers to return code objects - Fixed test matchers (toBeCalled → toHaveBeenCalled) - Added jest-environment-jsdom for Jest 28+ compatibility - Removed deprecated testRunner configuration Dev server: - Configured port 3000 as default - Updated client configuration for WebSocket connections - Migrated to new middleware registration pattern * fix: address PR feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Library, etc.) installed long enough for TypeScript to scan our test files; once they’re pruned the build proceeded
exactly like CI, fixing the missing-module error.
as part of the install.
CorpusItemPage.
current and type-safe.
Todos
Have you followed the guidelines in our Contributing document? Yes
Deployment
Standard deployment. After merging, trigger the usual CI/CD pipeline so the rebuilt image (with the
updated Dockerfile flow) is published.
Reference
Tickets: