@veryfront/ext-observability-sentry-node 0.1.1186 → 0.1.1189

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.
Files changed (2) hide show
  1. package/README.md +4 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -10,10 +10,10 @@ VERYFRONT_ERROR_REPORTER=sentry
10
10
  SENTRY_DSN=https://public@example.ingest.sentry.io/1
11
11
  ```
12
12
 
13
- `SENTRY_ENABLED=false` always disables reporting, even when the adapter and a
14
- valid DSN are present. During the compatibility rollout, an unset flag keeps
15
- the existing adapter-selection behavior. `SENTRY_DSN` selects the event
16
- destination and may use a public HTTPS custom Sentry hostname; `SENTRY_URL` is
13
+ Only `SENTRY_ENABLED=true` or `SENTRY_ENABLED=1` enables reporting. An unset,
14
+ blank, `false`, `0`, or unrecognized value disables reporting even when the
15
+ adapter and a valid DSN are present. `SENTRY_DSN` selects the event destination
16
+ and may use a public HTTPS custom Sentry hostname; `SENTRY_URL` is
17
17
  release-tooling configuration and is not read by the runtime adapter.
18
18
 
19
19
  `SENTRY_DSN` alone does not activate the framework adapter. Official compiled Veryfront
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@veryfront/ext-observability-sentry-node",
3
- "version": "0.1.1186",
3
+ "version": "0.1.1189",
4
4
  "description": "Veryfront first-party extension package for ext-observability-sentry-node",
5
5
  "keywords": [
6
6
  "veryfront",
@@ -27,7 +27,7 @@
27
27
  },
28
28
  "scripts": {},
29
29
  "engines": {
30
- "node": ">=18.0.0"
30
+ "node": ">=22.3.0"
31
31
  },
32
32
  "publishConfig": {
33
33
  "access": "public"