add sendPayloadChecksums config option and implement Bugsnag-Integrit…

[djskinner]

Goal

Add Bugsnag-Integrity request header (where required APIs are available) and implement the sendPayloadChecksums core config option to allow opting out of this behavior.

Bugsnag-Integrity headers are set by default unless the endpoint configuration option is set, in which case they are disabled. This behavior can be overriden with the new sendPayloadChecksums config option.

Design

• Bugsnag-Integrity headers are set where the environment supports it (requires native promises, subtle crypto, and a secure context)
• The behaviour of sendPayloadChecksums was chosen to avoid possible CORS issues where custom endpoints are being used and they are not configured to accept the new Bugsnag-Integrity in requests.

Changeset

• Add sendPayloadChecksums core config option
• Set Bugsnag-Integrity in delivery-fetch

Testing

• unit tests on delivery-fetch
• integration tests for browser
• e2e tests for browser

[github-actions[bot]]

Browser bundle size

NPM build

	Package
Before	210.63 kB
After	211.41 kB
±	+771 bytes ⚠️

CDN build

	Unminified	Minfied	Minified + gzipped
Before	107.59 kB	40.60 kB	11.89 kB
After	109.22 kB	41.21 kB	12.10 kB
±	+1,635 bytes ⚠️	+617 bytes ⚠️	+206 bytes ⚠️

Code coverage

Ok	File (✨=New File)	Lines	Branches	Functions	Statements
🔴	/home/runner/work/bugsnag-js-performance/bugsnag-js-performance/packages/core/lib/core.ts	100% (+0%)	90.9% (-2.85%)	92.85% (+0%)	98.5% (+0.04%)
🔴	/home/runner/work/bugsnag-js-performance/bugsnag-js-performance/packages/delivery-fetch/lib/delivery.ts	97.05% (+1.4%)	94.73% (-5.27%)	100% (+0%)	97.05% (+1.4%)

Total:

Lines	Branches	Functions	Statements
87.9%(+0.08%)	78.98%(+0.22%)	86.78%(+0.08%)	86%(+0.08%)

Generated against 5542818332c6382dccd9b301f5a6cbc8a4d5523e on 27 November 2024 at 14:23:04 UTC