@pagopa/azure-tracing 0.4.3-beta.1 → 0.4.4-beta.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,9 +22,7 @@ which makes direct instrumentation of Azure Functions a bit tricky.
|
|
|
22
22
|
So, if you have a Node.js project ESM based (`"type": "module"` in the `package.json`), to work around this, you have to preload the instrumentation logic at runtime using the `NODE_OPTIONS` environment variable.
|
|
23
23
|
|
|
24
24
|
> [!NOTE]
|
|
25
|
-
> In case you have a CJS project (`"type": "commonjs"` in the `package.json`), you could use the
|
|
26
|
-
> to instrument the application, making sure the OpenTelemetry SDK is initialized before the Azure Functions runtime starts.
|
|
27
|
-
> This package is useful for ESM projects only, where the instrumentation logic needs to be preloaded.
|
|
25
|
+
> In case you have a CJS project (`"type": "commonjs"` in the `package.json`), you could use the `@pagopa/azure-tracing` as well.
|
|
28
26
|
|
|
29
27
|
This package provides a wrapper that simplifies this setup.
|
|
30
28
|
|
package/package.json
CHANGED