Skip to content

Conversation

@lubianat
Copy link

@lubianat lubianat commented Nov 10, 2025

Building upon Will's

In relation to that, I've experimented on extracting out some parts of renderImage and on using https://www.npmjs.com/package/pngjs for testing without a browser

I've rolled back on JSdom for that, but we can go that path anyways

Will added "next step would be for you to

  • open a PR directly against the main repo and
  • add github action to run the tests for open PRs etc. "

Fixes #18.

will-moore and others added 9 commits November 4, 2025 12:05
- Uses https://www.npmjs.com/package/pngjs

- Separates rendering of data url in DOM/browser (canvas)
from rendering in node/testing (pngjs)

- For testing, data URLs are different; using decoded pixel bytes
- Setting longer timeout, as tests make calls that can take a few secs
- Updating package.json and tsconfig.json to account for the new parts
@will-moore
Copy link
Collaborator

Tests are running 👍
But failing:

npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.

Note: running npm install with my npm version normalized package-lock.json and removed per-package license fields;

happy to adjust if the project prefers a specific npm version / lockfile format.
@lubianat
Copy link
Author

lubianat commented Nov 11, 2025

@lubianat tried fixing it here; workflow re-running needs approval

@will-moore
Copy link
Collaborator

Build is green and tests passed 👍 Thanks...

brb..

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.

Test library using framework

2 participants