Skip to content

Alias resolve-url-loader to the Stackline continuation - #376

Open
alexandroit wants to merge 1 commit into
zaproxy:mainfrom
alexandroit:stackline/resolve-url-loader
Open

Alias resolve-url-loader to the Stackline continuation#376
alexandroit wants to merge 1 commit into
zaproxy:mainfrom
alexandroit:stackline/resolve-url-loader

Conversation

@alexandroit

Copy link
Copy Markdown

This updates the Sass loader chain's existing resolve-url-loader dependency without changing webpack.config.js or its historical require.resolve('resolve-url-loader') lookup. The manifest keeps that dependency key and points it to the exact npm alias npm:@stackline/resolve-url-loader@1.0.0; yarn.lock records the corresponding immutable registry artifact.

The concrete use is the loader entry at webpack.config.js:127, between css-loader and sass-loader. The compatibility continuation preserves the callable CommonJS loader, its existing options and deep entries, Webpack 4/5 behavior, and Node 12+ support. This is a maintenance-continuity change, not a vulnerability fix.

Validation on Node 24.19.0 and Yarn 1.22.22:

  • yarn install --frozen-lockfile
  • yarn lint
  • yarn test unitTests --runInBand — 2 suites, 27 tests passed
  • yarn run build — all six full/recorder Chrome, Firefox, and Opera production bundles passed
  • focused installed-package smoke — historical-key require, callable root, five helper functions, and deep lib/value-processor.js entry passed

The two Webpack output hashes matched the clean baseline. Existing lint warnings about the TypeScript parser range/React detection and the existing Webpack optimizeChunkAssets deprecation remain unchanged. I could not reproduce the repository's full Edge/Firefox integration matrix locally; repository CI remains the authority for that matrix. A clean baseline Chrome integration run had one intermittent frame-event case out of 66, and that exact case passed immediately in isolation.

Disclosure: I (alexandroit) maintain the independent @stackline/resolve-url-loader package proposed here. I am not affiliated with ZAP or the original resolve-url-loader maintainers.

References:

Signed-off-by: Alexandro Paixao Marques <aleinfoit@gmail.com>
@alexandroit
alexandroit force-pushed the stackline/resolve-url-loader branch from e8440c9 to 66e54b8 Compare August 28, 2026 12:44
@psiinon

psiinon commented Aug 28, 2026

Copy link
Copy Markdown
Member

Logo
Checkmarx One – Scan Summary & Detailsce6b0554-4166-412c-a981-1014732c2de4

Great job! No new security vulnerabilities introduced in this pull request


Use @Checkmarx to interact with Checkmarx PR Assistant.
Examples:
@Checkmarx how are you able to help me?
@Checkmarx rescan this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants