feat(openfeature): vendor the flagging provider instead of an optional peer

`@datadog/openfeature-node-server` was an optional peer dependency resolved
through a bundler-opaque require, requiring dedicated esbuild/webpack plugin
code to keep the require invisible when the peer wasn't installed (#8635) and
to inline it so bundles survived relocation when it was (#8980). Vendoring the
provider into `vendor/dist/` removes the need for a peer at all, so all of
that machinery (`feature-registry.js`, `register.js`, `require-provider.js`,
the optional-peer esbuild/webpack loaders, and their integration tests) is
deleted in favor of a single lazy `tracer.openfeature` property.

The vendored provider's only remaining external dependency is
`@openfeature/server-sdk`, used solely for `OpenFeatureEventEmitter` and
`ProviderEvents`. Bundling our own copy would give those a different identity
than the customer's, so it's externalized to a small bridge module
(`server-sdk-bridge.js`) that a new `openfeature-server-sdk` instrumentation
fills in from the customer's own `require()`.

`FlaggingProvider#initialize` also unrefs the vendored provider's
initialization timer, which otherwise keeps an idle process (a short script, a
serverless handler) alive for up to `initializationTimeoutMs` while waiting
for configuration to arrive. TODO left to remove this once
`@datadog/openfeature-node-server` unrefs it upstream.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: rochdev

LICENSE-3rdparty.csv

@@ -16,6 +16,8 @@
 "@jsep-plugin/assignment","https://github.com/EricSmekens/jsep","['MIT']","['Shelly']"
 "@jsep-plugin/regex","https://github.com/EricSmekens/jsep","['MIT']","['Shelly']"
 "@napi-rs/wasm-runtime","https://github.com/napi-rs/napi-rs","['MIT']","['LongYinan']"
+"@openfeature/core","https://github.com/open-feature/js-sdk","['Apache-2.0']","['OpenFeature Maintainers']"
+"@openfeature/server-sdk","https://github.com/open-feature/js-sdk","['Apache-2.0']","['OpenFeature Maintainers']"
 "@opentelemetry/api","https://github.com/open-telemetry/opentelemetry-js","['Apache-2.0']","['OpenTelemetry Authors']"
 "@opentelemetry/api-logs","https://github.com/open-telemetry/opentelemetry-js","['Apache-2.0']","['OpenTelemetry Authors']"
 "@opentelemetry/core","https://github.com/open-telemetry/opentelemetry-js","['Apache-2.0']","['OpenTelemetry Authors']"

README.md

@@ -93,24 +93,6 @@ 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 in a bundled application, require it through the
-`dd-trace/openfeature` subpath. This subpath uses a plain `require`/`import` for its dependencies, so
-bundlers can resolve and include them at build time. It must be loaded after `tracer.init()`:
-
-CommonJS:
-
-```js
-const tracer = require('dd-trace').init()
-const openfeatureProvider = require('dd-trace/openfeature')
-```
-
-ES modules: initialize the tracer with the `--import` flag (see the [ESM support](#ecmascript-modules-esm-support)
-section above) so it's ready before your application code runs, then import the provider normally:
-
-```js
-import openfeatureProvider from 'dd-trace/openfeature.js'
-```
-
 
 ## Security Vulnerabilities
 

index.d.ts

@@ -163,7 +163,6 @@ interface Tracer extends opentracing.Tracer {
    * @env DD_FEATURE_FLAGS_ENABLED
    * @env DD_FEATURE_FLAGS_CONFIGURATION_SOURCE
    * @beta This feature is in preview and not ready for production use
-   * @deprecated Use `require('dd-trace/openfeature')` instead, which also works in bundled applications.
    */
   openfeature: tracer.OpenFeatureProvider;
 

index.d.v5.ts

@@ -163,7 +163,6 @@ interface Tracer extends opentracing.Tracer {
    * @env DD_FEATURE_FLAGS_ENABLED
    * @env DD_FEATURE_FLAGS_CONFIGURATION_SOURCE
    * @beta This feature is in preview and not ready for production use
-   * @deprecated Use `require('dd-trace/openfeature')` instead, which also works in bundled applications.
    */
   openfeature: tracer.OpenFeatureProvider;
 

integration-tests/esbuild/build-and-test-openfeature.js

@@ -95,12 +95,6 @@ esbuildVersions.forEach((version) => {
       })
     })
 
-    it('bundles the optional OpenFeature peer so it survives bundle relocation', () => {
-      execSync('node ./build-and-test-openfeature.js', {
-        timeout,
-      })
-    })
-
     it('injects Git metadata into bundled applications', () => {
       execSync('node ./build-and-test-git-tags.js', {
         timeout,

integration-tests/esbuild/index.spec.js

@@ -58,10 +58,6 @@ webpackVersions.forEach((version) => {
       execSync('node ./build-and-test-skip-external.js', { timeout })
     })
 
-    it('does not follow `@datadog/openfeature-node-server` into its optional peer chain', () => {
-      execSync('node ./build-and-test-openfeature.js', { timeout })
-    })
-
     it('injects Git metadata into bundled applications', () => {
       execSync('node ./build-and-test-git-tags.js', { timeout })
     })