Use Case

zstd@2.0.0-alpha.0 had a few issues:

• We don't build and publish a macos x64 prebuild
• the entrypoint for the package points to the wrong file
• the gypfile is not included in the package

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• We don't build and publish a macos x64 prebuild
  • publish the arm64 build as the x64 build
  • make the arm64 build a universal binary
• the entrypoint for the package points to the wrong file
  • update `main` in the package.json to `lib/index.js`
• the gypfile is not included in the package
  • ensure all files are included in the package

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward