fix(deps): alias image-size to image-size-next@1.2.2 (CVE-2025-71329/71330)

[lcf2212dev]

Why this PR

This follow-up is for saplingjs/sapling: Static site generator that injects width/height on images at build time. Default master lists image-size@^1.0.0 in dependencies.

Published @sapling/sapling still depends on image-size@^1.0.0. Upstream image-size is archived. That coordinate remains affected by:

• CVE-2025-71329 / GHSA-5p2g-fcmc-qvqq — DoS via infinite loop on JXL/HEIF/JP2 zero-size boxes
• CVE-2025-71330 / GHSA-w3rx-r6r6-pgpr — DoS via infinite loop on ICNS zero entry length

There is no patched release on the original package name. npm audit fix cannot rename the coordinate. This is a follow-up to #606 with a one-line alias so installs stop fetching the vulnerable tarball.

Change

Alias the published 1.x dependencies entry in package.json:

- "image-size": "^1.0.0"
+ "image-size": "npm:image-size-next@1.2.2"

The npm lockfile alias was updated so npm ci stays in sync.

Call sites left untouched:

• lib/Uploads.js:14:import imageSize from 'image-size';
• test/lib/Uploads.test.js:6:import imageSize from 'image-size';

image-size-next@1.2.2 is a MIT community fork with the same 1.x public API. Compare: lcf2212dev/image-size-next@v1.2.1...v1.2.2

This is the 1.x pin (CJS default-export require('image-size') / import sizeOf from 'image-size'). Do not use image-size-next@2.1.1 here (ESM+CJS 2.x named imageSize export).

Hub: lcf2212dev/image-size-next#3

I maintain image-size-next and am not affiliated with the original image-size author, nor with this project. Happy to drop the alias if you prefer vendoring the size helper.

Test plan

• install resolves image-size → image-size-next@1.2.2
• existing require/import of image-size needs no source edits
• image width/height behaviour on the call sites above is unchanged