Feat/optional arch specific binaries #605
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following PR will fix #602
support libpact_ffi & pact-js-core node bindings to be published in seperate npm packages.
these are segmented by
${os}-{arch}-{libc}
users should not need to require these automatically, npm should determine the required
optional dependency to download at install time.
supported_platforms
CI Improvements
Significant build time reductions, by reducing the times when prebuilds are created.
This could be further improved to
native
or thebindings.gyp
changesTesting
Consumed in pact-js, via scoped publish, shown tested in following forked PR
Published for testing
Tested with
See example workflow / simple project
https://github.com/YOU54F/pact-js-packagers-test/blob/main/.github/workflows/test.yml