fix(build): add .ts extension to prod webpack configs (Node ≥21) #2352
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.
Description
This PR fixes the “Failed to load …webpack.config.base / ERR_MODULE_NOT_FOUND” build error that occurs on Node ≥ 21 (22 / 23 on Arch, Fedora, etc.).
Main changes
.erb/configs/webpack.config.main.prod.ts
.erb/configs/webpack.config.renderer.prod.ts
changed
to
Purpose
Node 21+ enforces explicit file-extensions for ESM imports.
Adding
.ts
lets the prod Webpack configs resolve correctly, restoring a clean build on modern Node without requiring--experimental-specifier-resolution=node
flags or downstream patches.Additional Notes
npm run build
andnpm run dev
both succeed, and the app launches correctly.ERR_MODULE_NOT_FOUND
when building on Node 22+).Contributor Agreement
By submitting this Pull Request, I confirm that I have read and agree to the following terms:
Please check the box below to confirm: