chore(deps): update dependency webpack to v5.104.1 [security]#6614
chore(deps): update dependency webpack to v5.104.1 [security]#6614renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit db2d17c
☁️ Nx Cloud last updated this comment at |
5e49ff6 to
e454c3a
Compare
4969128 to
cea543d
Compare
cea543d to
4e6cb37
Compare
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
4e6cb37 to
0652e50
Compare
162a195 to
b94e64d
Compare
ee9df68 to
a4fb797
Compare
8e70d00 to
a48cde7
Compare
18f011b to
53a04c6
Compare
53a04c6 to
868c139
Compare
6fdb823 to
3cdafd7
Compare
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that the failing CI tasks (@tanstack/eslint-plugin-start:build and @tanstack/eslint-plugin-router:build) are caused by pre-existing TypeScript type compatibility issues unrelated to this webpack security update. The same failures were confirmed to exist in an independent branch (6508), ruling out this PR as the root cause. No changes are needed here — these failures should be addressed separately.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
3cdafd7 to
54a811a
Compare
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and determined they are pre-existing TypeScript type incompatibilities in @eslint/core, @typescript-eslint/utils, and @tanstack/query — none of which are related to the webpack security update in this PR. The same failures are reproducible in other branches (e.g., branch 6508), confirming they were present before this change was introduced.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
54a811a to
1231195
Compare
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that these build failures are caused by a conflicting resolution of @typescript-eslint/utils (v8.53.0 vs v8.57.1) across the monorepo — a side effect of the lockfile being regenerated during the webpack security upgrade, not an intentional code change. Our recommendation is to resolve the peer dependency conflict by aligning @typescript-eslint/utils to a single version across the workspace before merging.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
1231195 to
c921c9c
Compare
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that the CI failures in @tanstack/eslint-plugin-start:build and @tanstack/eslint-plugin-router:build are pre-existing TypeScript type incompatibilities (TS2742, TS2345) related to ESLint and @typescript-eslint/utils version mismatches — not caused by the webpack update. The same failures were confirmed in branch 6508, which is unrelated to this PR, indicating an environment-level issue that exists independently of this change.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified the CI failures as pre-existing TypeScript type errors — including an @typescript-eslint/utils version mismatch and Query type incompatibilities — that also appear in unrelated branch 6508, confirming they were not introduced by this webpack update. Our recommendation is to address these underlying type issues separately and re-run CI on this PR once resolved.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified the CI failures as pre-existing TypeScript type incompatibility errors unrelated to this webpack security update — the same failures are present in other branches. Our analysis confirms these failures are not caused by the webpack upgrade from v5.97.1 to v5.104.1 and should not block this PR.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that the CI failures in @tanstack/eslint-plugin-start:build and @tanstack/eslint-plugin-router:build are pre-existing TypeScript type incompatibility issues unrelated to this webpack security update. The same failures were confirmed to exist in other branches, indicating these are not introduced by our changes here.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important

Nx Cloud has identified a possible root cause for your failed CI:
We reviewed the CI failures and determined they are pre-existing issues unrelated to this webpack security update. The TypeScript type errors in vue-query and the HMR e2e test timeouts are confirmed to exist in other branches as well. This PR can be merged once those unrelated failures are resolved upstream.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures on this PR and determined they are pre-existing issues unrelated to the webpack security update. The same TypeScript type errors (Vue Query tagged key incompatibilities) and ESLint plugin build failures were confirmed to exist in other independent branches. No changes are needed in this PR to address these failures.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that the failures are not caused by the webpack update itself, but by incompatible transitive dependency versions pulled in during lockfile regeneration — specifically @typescript-eslint/utils (8.53.0 → 8.57.1), @eslint/core, and @tanstack/vue-query. These packages introduced breaking TypeScript type changes across the eslint plugins and Vue e2e examples, none of which were directly modified by this PR.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and determined they are pre-existing issues unrelated to this webpack security update. The same 18 tasks are failing identically in branch 6508, confirming these TypeScript type errors and build failures exist independently of this PR. No changes are needed here — the webpack upgrade itself is safe to merge.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and confirmed they are pre-existing issues unrelated to this webpack security update. The same TypeScript type errors and test failures appear identically in other branches, indicating they were present before this PR was opened. No action is needed on this PR to address these failures.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We classified these failures as pre-existing environment state rather than code changes introduced by this PR. The failing tasks — TypeScript type errors in ESLint plugins, Vue/React router type checks, and E2E tests — are unrelated to a webpack version bump and were confirmed to exist identically on branch 6508. Our recommendation is to merge this security fix and address the pre-existing failures separately.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the failing tasks and found that the identical failures (TypeScript type errors, build failures, and E2E test failures) are present in an unrelated branch (6508), confirming these are pre-existing issues in the repository. Since this PR only bumps webpack from v5.97.1 to v5.104.1 as a security fix and touches no application code, these failures cannot be attributed to this change.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and determined they are pre-existing issues unrelated to this webpack security upgrade. The same failures appear in branch 7325, confirming they stem from a @typescript-eslint/utils version mismatch and other infrastructure issues that exist independently of our dependency bump.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We determined that all 18 failing tasks are pre-existing failures unrelated to this webpack security update, as the same errors (TypeScript type incompatibilities across @tanstack/vue-router, @tanstack/react-router, and related e2e projects) are reproducible in branch 7326. Our classification is environment_state — these failures need to be resolved independently of this PR.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and determined they are pre-existing issues unrelated to this webpack security bump. The failures — TypeScript type incompatibilities in vue-query, E2E HMR assertion mismatches, and ESLint plugin build errors — are confirmed to exist identically in the main branch. This PR can be merged safely once the underlying issues in main are resolved.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We classified these CI failures as a pre-existing environment state issue rather than a regression introduced by this PR. The same TypeScript type incompatibilities (eslint.config.js @eslint/core reference errors and RuleModule mismatches) are reproducible in branch "7326", confirming they existed before this webpack security update was opened. Since the PR contains zero source file changes beyond the lockfile bump, it cannot be the root cause of these failures.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures on this PR and confirmed they are pre-existing issues unrelated to the webpack security update. The same TypeScript type errors and test failures were found in branch 7326, proving they existed before this change was introduced.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We were unable to classify these failures as a direct code change because the PR diff shows 0 files changed, making it impossible to trace errors to specific lines. The failures — TypeScript branded type incompatibilities in @tanstack/query-core, an @typescript-eslint/utils version mismatch, and HMR test errors — are unrelated to webpack and likely stem from transitive lockfile dependency bumps introduced alongside the webpack update.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the CI failures and determined they are pre-existing TypeScript type incompatibility errors in the Vue Router/TanStack Query integration, unrelated to this webpack security bump. The same failures were confirmed to exist identically in branch 7326, indicating they predate this PR. Our recommendation is to merge this security update and address the type errors separately.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated the failing tasks and found that the same errors appear on branch 7326, which is unrelated to this webpack security update. The failures involve pre-existing TypeScript type incompatibilities in @tanstack/eslint-plugin-router and Vue Router packages — issues with no logical connection to the webpack version bump — and are therefore not caused by this PR.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We determined these failures are pre-existing environment issues, not caused by this PR — the same failures were confirmed in branch 7326, an unrelated branch. The errors involve TypeScript type incompatibilities in Vue Router/Vue Query integrations and @typescript-eslint/utils version mismatches, none of which are related to the webpack 5.97.1 → 5.104.1 security update. Our recommendation is to merge this security fix and address the pre-existing type/build failures separately.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We identified that all failing tasks — including TypeScript build errors in the ESLint plugins and various e2e/unit test failures — are pre-existing issues confirmed to also appear in unrelated branch 7326. Since none of the failures are related to the webpack dependency being updated here, this PR is not the cause of the CI failures.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
There was a problem hiding this comment.
Nx Cloud has identified a possible root cause for your failed CI:
We investigated all 20 failing tasks and found that the identical failures — TypeScript type errors around Vue query options and e2e/unit test failures — also appear in the independent branch 7326, confirming they are pre-existing issues unrelated to this PR. This change exclusively bumps webpack for a security fix and does not touch any application code, type definitions, or tests. No action is needed on this PR for those failures.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
This PR contains the following updates:
5.97.1→5.104.1webpack buildHttp HttpUriPlugin allowedUris bypass via HTTP redirects → SSRF + cache persistence
CVE-2025-68157 / GHSA-38r7-794h-5758
More information
Details
Summary
When
experiments.buildHttpis enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) enforcesallowedUrisonly for the initial URL, but does not re-validateallowedUrisafter following HTTP 30x redirects. As a result, an import that appears restricted to a trusted allow-list can be redirected to HTTP(S) URLs outside the allow-list. This is a policy/allow-list bypass that enables build-time SSRF behavior (requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion in build outputs (redirected content is treated as module source and bundled). In my reproduction, the internal response is also persisted in the buildHttp cache.Details
In the HTTP scheme resolver, the allow-list check (
allowedUris) is performed when metadata/info is created for the original request (viagetInfo()), but the content-fetch path follows redirects by resolving theLocationURL without re-checking whether the redirected URL is withinallowedUris.Practical consequence: if an “allowed” host/path can return a 302 (or has an open redirect), it can point to an external URL or an internal-only URL (SSRF). The redirected response is consumed as module content, bundled, and can be cached. If the redirect target is attacker-controlled, this can potentially result in attacker-controlled JavaScript being bundled and later executed when the resulting bundle runs.
Figure 1 (evidence screenshot): left pane shows the allowed host issuing a 302 redirect to
http://127.0.0.1:9100/secret.js; right pane shows the build output confirming allow-list bypass and that the secret appears in the bundle and buildHttp cache.PoC
This PoC is intentionally constrained to 127.0.0.1 (localhost-only “internal service”) to demonstrate SSRF behavior safely.
1) Setup
2) Create server.js
3) Create attacker.js
4) Run
Terminal A:
Terminal B:
5) Expected
Expected: Redirect target should be rejected if not in allowedUris (only http://127.0.0.1:9000/ is allowed).
Impact
Vulnerability class: Policy/allow-list bypass leading to SSRF behavior at build time and untrusted content inclusion in build outputs (and potentially bundling of attacker-controlled JavaScript if the redirect target is attacker-controlled).
Who is impacted: Projects that enable experiments.buildHttp and rely on allowedUris as a security boundary (to restrict remote module fetching). In such environments, an attacker who can influence imported URLs (e.g., via source contribution, dependency manipulation, or configuration) and can cause an allowed endpoint to redirect can:
trigger network requests from the build machine to internal-only services (SSRF behavior),
cause content from outside the allow-list to be bundled into build outputs,
and cause fetched responses to persist in build artifacts (e.g., buildHttp cache), increasing the risk of later exfiltration.
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
webpack buildHttp: allowedUris allow-list bypass via URL userinfo (@) leading to build-time SSRF behavior
CVE-2025-68458 / GHSA-8fgc-7cc6-rx7x
More information
Details
Summary
When
experiments.buildHttpis enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) can be bypassed to fetch resources from hosts outsideallowedUrisby using crafted URLs that include userinfo (username:password@host). IfallowedUrisenforcement relies on a raw string prefix check (e.g.,uri.startsWith(allowed)), a URL that looks allow-listed can pass validation while the actual network request is sent to a different authority/host after URL parsing. This is a policy/allow-list bypass that enables build-time SSRF behavior (outbound requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion (the fetched response is treated as module source and bundled). In my reproduction, the internal response was also persisted in the buildHttp cache.Reproduced on:
Details
Root cause (high level):
allowedUrisvalidation can be performed on the raw URI string, while the actual request destination is determined later by parsing the URL (e.g.,new URL(uri)), which interprets the authority as the part after@.Example crafted URL:
http://127.0.0.1:9000@​127.0.0.1:9100/secret.jsIf the allow-list is
["http://127.0.0.1:9000"], then:crafted.startsWith("http://127.0.0.1:9000")→ truenew URL()will contact):origin→http://127.0.0.1:9100(host/port after@)As a result, webpack fetches
http://127.0.0.1:9100/secret.jseven thoughallowedUrisonly includedhttp://127.0.0.1:9000.Evidence from reproduction:
[internal] 200 /secret.js served (...)(observed multiple times)PoC
This PoC is intentionally constrained to 127.0.0.1 (localhost-only “internal service”) to demonstrate SSRF behavior safely.
1) Setup
2) Create server.js
2) Create server.js
4) Run
Terminal A:
Terminal B:
5) Expected vs Actual
Expected: The import should be blocked because the effective request destination is http://127.0.0.1:9100/secret.js, which is outside allowedUris (only http://127.0.0.1:9000 is allow-listed).
Actual: The crafted URL passes the allow-list prefix validation, webpack fetches the internal-only resource on port 9100 (confirmed by server logs), and the secret marker appears in the bundle and buildHttp cache.
Impact
Vulnerability class: Policy/allow-list bypass leading to build-time SSRF behavior and untrusted content inclusion in build outputs.
Who is impacted: Projects that enable experiments.buildHttp and rely on allowedUris as a security boundary. If an attacker can influence the imported HTTP(S) specifier (e.g., via source contribution, dependency manipulation, or configuration), they can cause outbound requests from the build environment to endpoints outside the allow-list (including internal-only services, subject to network reachability). The fetched response can be treated as module source and included in build outputs and persisted in the buildHttp cache, increasing the risk of leakage or supply-chain contamination.
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
webpack/webpack (webpack)
v5.104.1Compare Source
Patch Changes
2efd21b: Reexports runtime calculation should not accessing WEBPACK_IMPORT_KEY decl with var.c510070: Fixed a user information bypass vulnerability in the HttpUriPlugin plugin.v5.104.0Compare Source
Minor Changes
d3dd841: Use method shorthand to render module content in__webpack_modules__object.d3dd841: Enhanceimport.meta.envto support object access.4baab4e: Optimize dependency sorting in updateParent: sort each module only once by deferring to finishUpdateParent(), and reduce traversal count in sortWithSourceOrder by caching WeakMap values upfront.04cd530: Handle more at-rules for CSS modules.cafae23: Added options to control the renaming of at-rules and various identifiers in CSS modules.d3dd841: Addedbase64url,base62,base58,base52,base49,base36,base32andbase25digests.5983843: Provide a stable runtime function variable__webpack_global__.d3dd841: ImprovedlocalIdentNamehashing for CSS.Patch Changes
22c48fb: Added module existence check for informative error message in development mode.50689e1: Use the fully qualified class name (or export name) for[fullhash]placeholder in CSS modules.d3dd841: Support universal lazy compilation.d3dd841: Fixed module library export definitions when multiple runtimes.d3dd841: Fixed CSS nesting and CSS custom properties parsing.d3dd841: Don't write fragment from URL to filename and apply fragment to module URL.aab1da9: Fixed bugs forcss/globaltype.d3dd841: Compatibilityimport.meta.filenameandimport.meta.dirnamewithevaldevtools.d3dd841: Handle nested__webpack_require__.728ddb7: The speed of identifier parsing has been improved.0f8b31b: Improve types.d3dd841: Don't corruptdebugIdinjection whenhidden-source-mapis used.2179fdb: Re-validate HttpUriPlugin redirects against allowedUris, restrict to http(s) and add a conservative redirect limit to prevent SSRF and untrusted content inclusion. Redirects failing policy are rejected before caching/lockfile writes.d3dd841: SerializeHookWebpackError.d3dd841: Added ability to use built-in properties in dotenv and define plugin.3c4319f: Optimizing the regular expression character class by specifying ranges for runtime code.d3dd841: Reduce collision for local indent name in CSS.d3dd841: Remove CSS link tags when CSS imports are removed.v5.103.0Compare Source
Features
DotenvPluginand top leveldotenvoption to enable this pluginWebpackManifestPluginignoreListoption in devtool pluginsimport.meta.envsupport for environment variablesimport.meta.dirnameandimport.meta.filenameimport.defer()for statistical pathimport file from "./file.json" with { type: "json" }__dirname/__filename/import.meta.dirname/import.meta.filenamefor universal targetexportTypeoption withlink(by default), "text" andcss-style-sheetvaluescomposespropertiesFixes
dependOnchunk must be loaded before the common chunkglobalThissupported__dirnameand__filenamefor ES modules__webpack_export__and__webpack_require__in already bundled codehashDigesttypev5.102.1Compare Source
Fixes
extendswithenvforbrowserslistJSONPfragment format for web workers.browserslist.commonjsexternals forSystemJSformat.import.metawarning messages to be more clear when used directly.v5.102.0Compare Source
Features
import file from "./file.ext" with { type: "bytes" }to get the content asUint8Array(look at example)import file from "./file.ext" with { type: "text" }to get the content as text (look at example)snapshot.contextModuleto configure snapshots options for context modulesextractSourceMapoption to implement the capabilities of loading source maps by comment, you don't needsource-map-loader(look at example)topLevelAwaitexperiment is now stable (you can removeexperiments.topLevelAwaitfrom yourwebpack.config.js)layersexperiment is now stable (you can removeexperiments.layersfrom yourwebpack.config.js)Fixes
thisexportstimeoutattribute of script tages-lexerformjsfiles for build dependencies__non_webpack_require__for ES moduleschunk.auxiliaryFilescreateRequireonly when output is ES module and target is nodePerformance Improvements
v5.101.3Compare Source
Fixes
v5.101.2Compare Source
Fixes
createRequirev5.101.1Compare Source
Fixes
processAdditionalAssetshookModuleFactoryclassGetChunkFilenamefailure caused bydependOnentrymodule.exportsbundle to ESM libraryRawModuleand condition ofisDeferredallowInlineStartupv5.101.0Compare Source
Fixes
output.environment.nodePrefixForCoreModulesoption everywhereoutput.importMetaNameoption everywhereFeatures
deferImportoption to parser optionsPerformance Improvements
requirein some placesv5.100.2Compare Source
Fixes
Performance Improvements
importPhasesPluginonly when enabledeferImport(#19689)v5.100.1Compare Source
Fixes
v5.100.0Compare Source
Fixes
Features
splitChunkswhen external variables and runtimeChunk are not set.usingkeywordnew URL(...)virtual:schemePerformance Improvements
new URL(...)evaluate expressionv5.99.9Compare Source
Fixes
v5.99.8Compare Source
Fixes
@types/nodev5.99.7Compare Source
Fixes
defaultreexport (#19463)causeof any errors anderrorsof AggregateError in stats output@types/json-schemain typesv5.99.6Compare Source
Fixes
modulelibrary when mixing commonjs and esm modulesFlagDependencyExportsPluginfor libraries where it requiredv5.99.5Compare Source
Fixes
v5.99.4Compare Source
Fixes
if/elsev5.99.3Compare Source
Fixes
if/elsev5.99.2Compare Source
Fixes
v5.99.1Compare Source
Fixes
v5.99.0Compare Source
Fixes
__proto__propertymoduleandmoduleESM libraries have been union and code generation has been improvedcommonjs-staticlibrarymeta.webpackASTxxhash64forcache.hashAlgorithmwhenexperiments.futureDefaultsenabledFeatures
new Worker(import.meta.url)andnew Worker(new URL(import.meta.url))syntaxPerformance Improvements
Chores
stricttypes fortypescriptv5.98.0Compare Source
Fixes
filenameTemplatein new split chunk #19104 by @henryqdineenblob:protocol when public path isauto#19199 by @alexander-akaitoutput.charseteverywhere #19202 by @alexander-akaitBuildInfoandBuildMetatype definitions #19200 by @inottnPerformance Improvements
FlagDependencyExportsPluginfor large JSON by depth #19058 by @hai-xstartsWithfor matching instead of converting the string to a regex #19207 by @inottnChores
nanoidfrom 3.3.7 to 3.3.8 #19063 by @dependabotDefaultStatsFactoryPlugin#19156 by @Andaristreadme.mdby adding video links for understanding webpack #19101 by @Vansh5632Features
/* webpackIgnore: true */forrequire.resolve#19201 by @alexander-akaitContinuous Integration
New Contributors
Full Changelog: webpack/webpack@v5.97.1...v5.98.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.