Skip to content

Adding Power support(ppc64le) with ci and testing to the project for architecture independent - #730

Closed
asellappen wants to merge 1 commit into
Stuk:mainfrom
asellappen:master
Closed

Adding Power support(ppc64le) with ci and testing to the project for architecture independent#730
asellappen wants to merge 1 commit into
Stuk:mainfrom
asellappen:master

Conversation

@asellappen

Copy link
Copy Markdown

Adding power support for this package to support arch independent

I am working for IBM to port cpu arch ppc64le for open sources.

This PR adds CI support for the IBM Power Little Endian (ppc64le) architecture. The idea is to ensure that the builds on this architecture are continuously tested along with the Intel builds (amd64) as this is part of the ubuntu distro
on that architecture as well and detecting (and fixing) any issues or failures early would help to ensure that we are always up to date.

This helps us simplify testing later when distributions are re-building and re-releasing,We typically build applications for customers and ISVs, and while we don't use this package directly, we do count on all of the packages in debian/ubuntu to build other packages. So we more likely have this as a second or third level dependency and couldn't tell you explicitly which features we use or our usage model.

Please help to verify and merge.

@jonkoops

jonkoops commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

Thanks for this work, and sorry it sat open so long.

This PR adds ppc64le jobs to .travis.yml. Travis is no longer used here. CI moved to GitHub Actions in #942, and .travis.yml has been removed from main.

jszip is pure JavaScript with no native bindings. The published package is the same on every architecture Node supports, so we do not test per CPU architecture upstream.

Closing as stale.

@jonkoops jonkoops closed this Sep 6, 2026
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.

2 participants