Repository navigation
refactor(libdatadog): keep data pipeline on WASM - #216
Merged
Merged
Conversation
The agentless exporter has no native consumer yet, so its N-API implementation duplicates the WASM exporter and its lifecycle. The default entry point now loads the WASM binding only when it creates an exporter. Refs: #205
Overall package sizeSelf size: 37.14 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
The native facade exposed the agentless exporter even though every export used WASM, which kept a false backend-parity contract.
The shared exporter imported the WASM workspace package directly, which root lint cannot resolve. Keeping binding ownership in the WASM facade also defers agentless transport loading until exporter creation.
BridgeAR
marked this pull request as ready for review
August 28, 2026 17:53
bengl
approved these changes
Aug 28, 2026
BridgeAR
force-pushed
the
BridgeAR/2026-08-28-data-pipeline-wasm-only
branch
from
August 28, 2026 19:51
2fb5932 to
2ac46c3
Compare
bengl
approved these changes
Aug 31, 2026
Merged
bengl
pushed a commit
that referenced
this pull request
Aug 31, 2026
* refactor(libdatadog): keep data pipeline on WASM The agentless exporter has no native consumer yet, so its N-API implementation duplicates the WASM exporter and its lifecycle. The default entry point now loads the WASM binding only when it creates an exporter. Refs: #205 * refactor(libdatadog): isolate native backend The native facade exposed the agentless exporter even though every export used WASM, which kept a false backend-parity contract. * fix(libdatadog): defer agentless implementation loading The shared exporter imported the WASM workspace package directly, which root lint cannot resolve. Keeping binding ownership in the WASM facade also defers agentless transport loading until exporter creation.
bengl
pushed a commit
that referenced
this pull request
Aug 31, 2026
* refactor(libdatadog): keep data pipeline on WASM The agentless exporter has no native consumer yet, so its N-API implementation duplicates the WASM exporter and its lifecycle. The default entry point now loads the WASM binding only when it creates an exporter. Refs: #205 * refactor(libdatadog): isolate native backend The native facade exposed the agentless exporter even though every export used WASM, which kept a false backend-parity contract. * fix(libdatadog): defer agentless implementation loading The shared exporter imported the WASM workspace package directly, which root lint cannot resolve. Keeping binding ownership in the WASM facade also defers agentless transport loading until exporter creation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 agentless exporter has no native consumer yet, so its N-API implementation duplicates the WASM exporter and its lifecycle.
createAgentlessExporter()now loads the WASM binding lazily. DDSketch and Zstandard still use the selected native or WASM backend.Refs: #205