@daisy/ace-report - npm Package Versions

1.2.1 (2021-04-09)

Bugfixes:

• The Puppeteer Axe "runner" wasn't handling XML / XHTML correctly with .html or .htm file extensions (the Electron runner was ok already)
• The HTTPS self-signed certificate validation procedure for the DAISY Knowledge Base was colliding with the HTTP server used in Ace with the Electron Axe runner.
• There was a random possibility of the Axe script not being ready in time for Ace.
• In case a single publication document causes a fatal error, the whole pool of concurrent validation windows is torn down, which caused timers to fire after disposal and attempt to reload now-defunct windows.

<a name="1.2.0"></a>

1.2.0 (2021-04-08)

Major internal update (see https://github.com/daisy/ace/pull/314 ).

Summary:

• Based on DAISY's own fork of Deque's Axe (latest v4 version), instead of patching Axe's distributed Javascript bundles (see https://github.com/daisy/axe-core/pull/4 )
• Better localization tooling for Axe, integration of Axe translations
• Two Axe "runners": Puppeteer (default for Ace CLI), and Electron (can be used in CLI, and used by Ace App), Chromium web browser engine is used in both cases, but Electron runner uses a HTTP server to simulate a typical reading system environment. Unit tests plumbing for both platforms (Continuous Integration server only executes the Puppeteer ones, for faster builds). Runtime performance is near-identical (there is a developer script to check this).
• NodeJS >=10 requirement
• NPM package dependencies updated to latest versions (except where NodeJS requirement is higher). Added developer scripts to facilitate version checking and incremental updates at regular intervals (i.e. package.json exact references and yarn.lock maintenance)
• All Ace sub-packages (@daisy/ organisation scope on NPM) have exact same semantic version (easier deployment with developer script that automates NPM publish)
• Fixes bugs that couldn't easily be fixed in Ace 1.1.1 (the last of v1), due to older Axe (v3 instead of v4) and due to older NPM package dependencies that were necessary for compatibility with legacy NodeJS requirement (now deprecated / deemed unsecure).

<a name="1.1.1"></a>