feat(libdatadog): add dedicated remote config WASM - #217
Merged
Conversation
Overall package sizeSelf size: 31.66 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
BridgeAR
marked this pull request as ready for review
August 28, 2026 19:25
BridgeAR
force-pushed
the
BridgeAR/2026-08-28-remote-config-wasm-only
branch
from
August 31, 2026 16:31
aacbc2e to
dd35542
Compare
Remote Config pulls in TUF, cryptography, and HTTP dependencies that existing users do not need. Keeping its artifact separate preserves the existing universal WASM load and compile cost.
The lint job runs before generated Remote Config modules exist, so fresh checkouts reject both wrapper imports. The request test also verifies that the storage hook wraps the HTTP request.
Package export maps can target the canonical CommonJS artifacts directly, so forwarding files own no format or compatibility boundary.
BridgeAR
force-pushed
the
BridgeAR/2026-08-28-remote-config-wasm-only
branch
from
August 31, 2026 16:43
64203ee to
ce856bd
Compare
bengl
approved these changes
Aug 31, 2026
Merged
bengl
pushed a commit
that referenced
this pull request
Aug 31, 2026
* feat(libdatadog): add dedicated remote config WASM Remote Config pulls in TUF, cryptography, and HTTP dependencies that existing users do not need. Keeping its artifact separate preserves the existing universal WASM load and compile cost. * ci(libdatadog): validate remote config entry point The lint job runs before generated Remote Config modules exist, so fresh checkouts reject both wrapper imports. The request test also verifies that the storage hook wraps the HTTP request. * refactor(libdatadog): simplify remote config packaging Package export maps can target the canonical CommonJS artifacts directly, so forwarding files own no format or compatibility boundary.
bengl
pushed a commit
that referenced
this pull request
Aug 31, 2026
* feat(libdatadog): add dedicated remote config WASM Remote Config pulls in TUF, cryptography, and HTTP dependencies that existing users do not need. Keeping its artifact separate preserves the existing universal WASM load and compile cost. * ci(libdatadog): validate remote config entry point The lint job runs before generated Remote Config modules exist, so fresh checkouts reject both wrapper imports. The request test also verifies that the storage hook wraps the HTTP request. * refactor(libdatadog): simplify remote config packaging Package export maps can target the canonical CommonJS artifacts directly, so forwarding files own no format or compatibility boundary.
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.
This packages the existing
crates/remote_configimplementation as a dedicated inline WASM artifact.@datadog/libdatadog/remote-configloads it without changing the root or./wasmentry points. Existing root and./wasmimports do not expose or compile Remote Config.The artifact ships inside the existing
@datadog/libdatadog-wasmpackage, so the release workflow and npm workspace layout stay unchanged. All installs download the artifact, but only Remote Config users pay its load and compile cost. This does not add a native or N-API implementation.The public subpaths target the canonical CommonJS artifacts directly. Node package export maps cannot target another package, so the metapackage keeps its required boundary adapter.
The dependency audit treats Remote Config as a separate artifact tree. It permits only the exact duplicate versions and Tokio paths in the current
libdd-remote-configgraph.Refs: #214