dd-trace 6.3.0 → 6.5.0

package/README.electron.md

@@ -0,0 +1,7 @@
+# dd-trace-electron
+
+> **Internal use only.**
+>
+> This package is intended to be used by the
+> [Datadog Electron SDK](https://github.com/DataDog/electron-sdk) and is not
+> meant for direct consumption. Only direct usage of `dd-trace` is supported.

package/README.md

@@ -93,6 +93,23 @@ Regardless of where you open the issue, someone at Datadog will try to help.
 
 If you would like to trace your bundled application then please read this page on [bundling and dd-trace](https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/#bundling). It includes information on how to use our ESBuild plugin and includes caveats for other bundlers.
 
+When using the experimental OpenFeature provider, file-traced deployments can force the optional provider and
+its dependencies into the output with a side-effect import before accessing `tracer.openfeature`:
+
+CommonJS:
+
+```js
+require('dd-trace/openfeature')
+```
+
+ES modules:
+
+```js
+import 'dd-trace/openfeature.js'
+```
+
+This is a fallback for build tools that do not recognize the provider's optional-require wrapper.
+
 
 ## Security Vulnerabilities