build: add an npm release command that builds and validates #113

Activity

1. hsd-bot commented on Oct 30, 2026

   

   hsd-bot

   on Oct 30, 2026

   CollaboratorAuthor

   More actions

   hsd: Implementation plan

   • Add npm run test:release (script in make/release-check.js). It:
     1. Copies the files npm pack would publish into a gitignored .release/ directory and runs make/build.js there, so the repo's committed imagediff.js/imagediff.min.js are left untouched.
     2. Runs the existing Node specs (library, load and CLI specs) once against the fresh imagediff.js via require of the staged package (its main), and once against imagediff.min.js. The CLI spec runs the staged bin/imagediff.
     3. Runs the existing browser specs in Chromium with the page loading each built file as a plain <script> global.
     4. With --committed (for release PRs), also fails unless the repo's imagediff.js and imagediff.min.js match the fresh build byte for byte.
   • The specs pick their target from env vars (IMAGEDIFF_LIBRARY, IMAGEDIFF_BIN) and the spec page from a ?lib= query param, defaulting to the source, so npm test is unchanged.
   • Document it in the README and CONTRIBUTING (run before publishing), and point chore(release): 2.0.0 #101 at it.
2. cesutherland

   changed the title [-]test: smoke-test the built release files[/-] [+]build: add an npm release command that builds and validates[/+] on Oct 30, 2026
3. hsd-bot commented on Oct 30, 2026

   

   hsd-bot

   on Oct 30, 2026

   CollaboratorAuthor

   More actions

   hsd: Implementation plan (rewritten ticket)

   PR #114 was closed unmerged, so the validation it added (pointing npm test at a built file with IMAGEDIFF_LIBRARY) isn't on master. I'll carry that forward unchanged and build the release commands on it:

   • npm run test:built runs npm test against imagediff.js and then imagediff.min.js, through require in Node and as a <script> global in the browser.
   • npm run release runs npm run build and then npm run test:built. It leaves the fresh files in place to commit, and doesn't tag or publish.
   • A prepublishOnly script refuses npm publish if the built files differ from what's committed (git diff against HEAD) and then runs npm run test:built. It doesn't rebuild.
   • Update the README and CONTRIBUTING release instructions to say to use npm run release. I can't edit chore(release): 2.0.0 #101 from here, so the PR will note the line it needs.

   This goes on a fresh branch from master, in a new PR, since #114 was closed.
4. cesutherland

   closed this as completedin #115on Oct 30, 2026