Skip to content

v3.5.1

Choose a tag to compare

@callinmullaney callinmullaney released this 28 Oct 21:15
87c700d

Maintenance release for the Webpack-based 3.x integration. Requires Node.js 24 or newer.

Installation fix

Core now requires Jest and jest-environment-jsdom ^30.5.2. This replaces the failing installation chain with:

@emulsify/core@3.5.1
└─ jest@30.5.2
   └─ @jest/core@30.5.2
      └─ jest-resolve@30.5.1
         └─ unrs-resolver@1.12.2

The resolver uses node postinstall.js and the helper's JavaScript API. It succeeds when the napi-postinstall CLI is non-executable. The old resolver 1.11.1 cannot satisfy Core's new dependency requirements, including when upgrading an existing 3.5.0 consumer lockfile.

Maintenance

  • Update compatible stable dependencies while retaining the Node >=24 contract, Webpack integration, configuration paths, commands, and output formats.
  • Remove the historical dependency overrides.
  • Replace obsolete native image executable installers with supported prebuilt codecs; preserve lossless PNG and progressive, lossless JPEG optimization.
  • Preserve legacy Sass glob imports and cleanup behavior through supported Sass, glob, and Webpack APIs.
  • Retain compatible Babel, Storybook, Emulsify CLI, Sass loader, YAML, and Twig versions where newer majors would require consumer changes.

See the complete dependency table and compatibility evidence.

Upgrade

Run in your project or theme, then commit the updated package manifest and lockfile:

npm install @emulsify/core@^3.5.1
npm ls @emulsify/core jest @jest/core jest-resolve unrs-resolver napi-postinstall
npm ci

Use npm install --save-dev @emulsify/core@^3.5.1 if Core is already a development dependency. Deleting the lockfile, project-specific overrides, and permission repair commands are unnecessary.

The maintenance npm channel is legacy-3. The newer 4.x line retains latest.

Validation and limitations

Validation covers macOS and Linux, tests and lint, production Webpack and static Storybook builds, fresh packed-consumer installation, upgrade from the exact 3.5.0/Jest 30.3.0/resolver 1.11.1 lockfile, subsequent npm ci, peer compatibility, and the non-executable-helper regression. Minimum Node 24.0.2 consumer checks also pass locally.

This is not a clean security audit: 33 repository audit records include 3 critical findings; fresh and historical consumer lockfiles report different totals. Three upstream deprecations remain. Exact owning dependencies, constraints, and consumer refresh guidance are documented in the audit and deprecation report. Optional macOS fsevents native-build warnings do not prevent installation or builds.

Validation details · Release pull request · npm package