Mirrors
/
matrix-public-archive
mirror of https://github.com/matrix-org/matrix-public-archive.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
matrix-public-archive/package-lock.json

9352 lines
220 KiB
JSON
Raw Normal View History

Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
{
"name": "matrix-public-archive",
"version": "0.0.0",
"lockfileVersion": 2,
"requires": true,
"packages": {
"": {
"name": "matrix-public-archive",
"version": "0.0.0",
Fix missing `room.observePowerLevels()` throwing error after render (#57) Fix missing `room.observePowerLevels()` throwing error after render. ``` Uncaught (in promise) TypeError: this._room.observePowerLevels is not a function at RoomViewModel2._recreateComposerOnPowerLevelChange (matrix-public-archive.js:23498:53) at new RoomViewModel2 (matrix-public-archive.js:23469:14) at mountHydrogen (matrix-public-archive.js:27131:25) at matrix-public-archive.js:27174:1 ``` Doesn't affect main-line rendering but the error is annoying to see. More Hydrogen boilerplate 😞
2022-08-30 22:40:07 -06:00
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.1.0",
"@opentelemetry/auto-instrumentations-node": "^0.31.0",
"@opentelemetry/context-async-hooks": "^1.4.0",
"@opentelemetry/core": "^1.4.0",
"@opentelemetry/exporter-jaeger": "^1.3.1",
"@opentelemetry/instrumentation": "^0.30.0",
"@opentelemetry/propagator-ot-trace": "^0.26.0",
"@opentelemetry/resources": "^1.3.1",
"@opentelemetry/sdk-trace-base": "^1.3.1",
"@opentelemetry/semantic-conventions": "^1.3.1",
"dompurify": "^2.3.9",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"express": "^4.17.2",
Fix missing `room.observePowerLevels()` throwing error after render (#57) Fix missing `room.observePowerLevels()` throwing error after render. ``` Uncaught (in promise) TypeError: this._room.observePowerLevels is not a function at RoomViewModel2._recreateComposerOnPowerLevelChange (matrix-public-archive.js:23498:53) at new RoomViewModel2 (matrix-public-archive.js:23469:14) at mountHydrogen (matrix-public-archive.js:27131:25) at matrix-public-archive.js:27174:1 ``` Doesn't affect main-line rendering but the error is annoying to see. More Hydrogen boilerplate 😞
2022-08-30 22:40:07 -06:00
"hydrogen-view-sdk": "npm:@mlm/hydrogen-view-sdk@^0.15.0-scratch",
Use JSON5 for configuration files with comments (#52) Use JSON5 for configuration files with comments. Now we can leave the available config in `config.default.json` without having to add weird instructions to remove the `xxx`, etc - https://www.npmjs.com/package/json5 - https://www.npmjs.com/package/nconf - https://github.com/indexzero/nconf/issues/113#issuecomment-69999413
2022-08-29 19:33:02 -06:00
"json5": "^2.2.1",
WIP: Add calendar to right panel
2022-02-14 20:11:55 -07:00
"linkedom": "^0.14.1",
Add custom RightPanel support
2022-02-10 01:21:49 -07:00
"matrix-public-archive-shared": "file:./shared/",
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"nconf": "^0.11.3",
Link calendar days
2022-02-16 18:58:32 -07:00
"node-fetch": "^2.6.7",
"url-join": "^4.0.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"devDependencies": {
Working e2e test
2022-02-24 02:27:53 -07:00
"escape-string-regexp": "^4.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"eslint": "^8.8.0",
"eslint-config-prettier": "^8.3.0",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-prettier": "^4.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"merge-options": "^3.0.4",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"mocha": "^9.2.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"nodemon": "^2.0.15",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"prettier": "^2.5.1",
Fix nodemon not being able to watch for changes because vite is interfering (#11) We use `vite@2.9.6` because `vite>=2.9.7` is interfering with `nodemon`, see https://github.com/vitejs/vite/issues/8492 This means that when using `npm run start-dev` -> [`start-dev.js`](https://github.com/matrix-org/matrix-public-archive/blob/40f9d2ea5afb74c4f04030fb1a643fcd803a70e7/server/start-dev.js), `nodemon` wasn't restarting when a change was made.
2022-06-07 13:56:46 -06:00
"vite": "^2.9.6"
Link calendar days
2022-02-16 18:58:32 -07:00
},
"engines": {
"node": ">=16.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"node_modules/@eslint/eslintrc": {
"version": "1.0.5",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
"ajv": "^6.12.4",
"debug": "^4.3.2",
"espree": "^9.2.0",
"globals": "^13.9.0",
"ignore": "^4.0.6",
"import-fresh": "^3.2.1",
"js-yaml": "^4.1.0",
"minimatch": "^3.0.4",
"strip-json-comments": "^3.1.1"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/@eslint/eslintrc/node_modules/debug": {
"version": "4.3.3",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@eslint/eslintrc/node_modules/ignore": {
"version": "4.0.6",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
"node": ">= 4"
}
},
"node_modules/@eslint/eslintrc/node_modules/ms": {
"version": "2.1.2",
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"dev": true,
"license": "MIT"
},
"node_modules/@fastify/ajv-compiler": {
"version": "1.1.0",
"license": "MIT",
"dependencies": {
"ajv": "^6.12.6"
}
},
"node_modules/@fastify/error": {
"version": "2.0.0",
"license": "MIT"
},
"node_modules/@hapi/b64": {
"version": "5.0.0",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "9.x.x"
}
},
"node_modules/@hapi/boom": {
"version": "9.1.4",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "9.x.x"
}
},
"node_modules/@hapi/bourne": {
"version": "2.1.0",
"license": "BSD-3-Clause"
},
"node_modules/@hapi/cryptiles": {
"version": "5.1.0",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/boom": "9.x.x"
},
"engines": {
"node": ">=12.0.0"
}
},
"node_modules/@hapi/hoek": {
"version": "9.3.0",
"license": "BSD-3-Clause"
},
"node_modules/@hapi/iron": {
"version": "6.0.0",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/b64": "5.x.x",
"@hapi/boom": "9.x.x",
"@hapi/bourne": "2.x.x",
"@hapi/cryptiles": "5.x.x",
"@hapi/hoek": "9.x.x"
}
},
"node_modules/@hapi/podium": {
"version": "4.1.3",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "9.x.x",
"@hapi/teamwork": "5.x.x",
"@hapi/validate": "1.x.x"
}
},
"node_modules/@hapi/teamwork": {
"version": "5.1.1",
"license": "BSD-3-Clause",
"engines": {
"node": ">=12.0.0"
}
},
"node_modules/@hapi/topo": {
"version": "5.1.0",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "^9.0.0"
}
},
"node_modules/@hapi/validate": {
"version": "1.1.3",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "^9.0.0",
"@hapi/topo": "^5.0.0"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"node_modules/@humanwhocodes/config-array": {
"version": "0.9.3",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
"@humanwhocodes/object-schema": "^1.2.1",
"debug": "^4.1.1",
"minimatch": "^3.0.4"
},
"engines": {
"node": ">=10.10.0"
}
},
"node_modules/@humanwhocodes/config-array/node_modules/debug": {
"version": "4.3.3",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@humanwhocodes/config-array/node_modules/ms": {
"version": "2.1.2",
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"dev": true,
"license": "MIT"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"node_modules/@humanwhocodes/object-schema": {
"version": "1.2.1",
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"dev": true,
"license": "BSD-3-Clause"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"node_modules/@matrix-org/olm": {
Use stable test selectors from Hydrogen (`data-testid`) Follow-up to https://github.com/matrix-org/matrix-public-archive/pull/29#discussion_r909492946 --- Updated Hydrogen to add the consistent `data-testid` attribute selectors, https://github.com/vector-im/hydrogen-web/pull/773 ``` npm install hydrogen-view-sdk@npm:@mlm/hydrogen-view-sdk@0.0.13-scratch ```
2022-07-05 05:23:47 -06:00
"version": "3.2.8",
"resolved": "https://gitlab.matrix.org/api/v4/projects/27/packages/npm/@matrix-org/olm/-/@matrix-org/olm-3.2.8.tgz",
"integrity": "sha512-yCJzEYY2aG1z+7nxKYZC4DFYwQO/5iG019qgotJhauYJRhEG9gLrKTvXO6lRHS8TjnZzsZFZyO/hQUlI4Dryig==",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"license": "Apache-2.0"
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/api": {
"version": "1.1.0",
"license": "Apache-2.0",
"engines": {
"node": ">=8.0.0"
}
},
"node_modules/@opentelemetry/api-metrics": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api": "^1.0.0"
},
"engines": {
"node": ">=8.12.0"
}
},
"node_modules/@opentelemetry/auto-instrumentations-node": {
"version": "0.31.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/instrumentation-amqplib": "^0.30.0",
"@opentelemetry/instrumentation-aws-lambda": "^0.32.0",
"@opentelemetry/instrumentation-aws-sdk": "^0.8.0",
"@opentelemetry/instrumentation-bunyan": "^0.29.0",
"@opentelemetry/instrumentation-cassandra-driver": "^0.29.0",
"@opentelemetry/instrumentation-connect": "^0.29.0",
"@opentelemetry/instrumentation-dns": "^0.29.0",
"@opentelemetry/instrumentation-express": "^0.30.0",
"@opentelemetry/instrumentation-fastify": "^0.28.0",
"@opentelemetry/instrumentation-generic-pool": "^0.29.0",
"@opentelemetry/instrumentation-graphql": "^0.29.0",
"@opentelemetry/instrumentation-grpc": "^0.29.2",
"@opentelemetry/instrumentation-hapi": "^0.29.0",
"@opentelemetry/instrumentation-http": "^0.29.2",
"@opentelemetry/instrumentation-ioredis": "^0.30.0",
"@opentelemetry/instrumentation-knex": "^0.29.0",
"@opentelemetry/instrumentation-koa": "^0.30.0",
"@opentelemetry/instrumentation-memcached": "^0.29.0",
"@opentelemetry/instrumentation-mongodb": "^0.31.0",
"@opentelemetry/instrumentation-mysql": "^0.30.0",
"@opentelemetry/instrumentation-mysql2": "^0.31.0",
"@opentelemetry/instrumentation-nestjs-core": "^0.30.0",
"@opentelemetry/instrumentation-net": "^0.29.0",
"@opentelemetry/instrumentation-pg": "^0.30.0",
"@opentelemetry/instrumentation-pino": "^0.30.0",
"@opentelemetry/instrumentation-redis": "^0.32.0",
"@opentelemetry/instrumentation-redis-4": "^0.31.0",
"@opentelemetry/instrumentation-restify": "^0.29.0",
"@opentelemetry/instrumentation-winston": "^0.29.0"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/auto-instrumentations-node/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/auto-instrumentations-node/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"bin": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/context-async-hooks": {
"version": "1.4.0",
"license": "Apache-2.0",
"engines": {
"node": ">=14"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/core": {
"version": "1.4.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.4.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=14"
},
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/core/node_modules/@opentelemetry/semantic-conventions": {
"version": "1.4.0",
"license": "Apache-2.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=14"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/exporter-jaeger": {
"version": "1.3.1",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "1.3.1",
"@opentelemetry/sdk-trace-base": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1",
"jaeger-client": "^3.15.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/exporter-jaeger/node_modules/@opentelemetry/core": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation": {
"version": "0.30.0",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.30.0",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=14"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-amqplib": {
"version": "0.30.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/amqplib": "^0.5.17"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10.0.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-amqplib/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-amqplib/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-lambda": {
"version": "0.32.0",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/propagator-aws-xray": "^1.1.0",
"@opentelemetry/resources": "^1.0.0",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/aws-lambda": "8.10.81"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-lambda/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-lambda/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-sdk": {
"version": "0.8.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/propagation-utils": "^0.28.0",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=12.0.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-sdk/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-aws-sdk/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"semver": "bin/semver.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-bunyan": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@types/bunyan": "1.8.7"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-bunyan/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-bunyan/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
"node": ">=10"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-cassandra-driver": {
"version": "0.29.0",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-cassandra-driver/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-cassandra-driver/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-connect": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/connect": "3.4.35"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-connect/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-connect/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-dns": {
"version": "0.29.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"semver": "^7.3.2"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-dns/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-dns/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-express": {
"version": "0.30.0",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/express": "4.17.13"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-express/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-express/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-fastify": {
"version": "0.28.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"fastify": "^3.19.2"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-fastify/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-fastify/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-generic-pool": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/generic-pool": "^3.1.9"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-generic-pool/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-generic-pool/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-graphql": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"graphql": "^15.5.1"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-graphql/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-graphql/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=10"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-grpc": {
"version": "0.29.2",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"@opentelemetry/instrumentation": "0.29.2",
"@opentelemetry/semantic-conventions": "1.3.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-grpc/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
},
"node_modules/@opentelemetry/instrumentation-grpc/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-hapi": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/hapi__hapi": "20.0.9"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-hapi/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-hapi/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-http": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "1.3.1",
"@opentelemetry/instrumentation": "0.29.2",
"@opentelemetry/semantic-conventions": "1.3.1",
"semver": "^7.3.5"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-http/node_modules/@opentelemetry/core": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-http/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-http/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-ioredis": {
"version": "0.30.0",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/ioredis": "4.26.6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-ioredis/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-ioredis/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-knex": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-knex/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-knex/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-koa": {
"version": "0.30.0",
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/koa": "2.13.4",
"@types/koa__router": "8.0.7"
},
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-koa/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-koa/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"bin": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver": "bin/semver.js"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-memcached": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/memcached": "^2.2.6"
},
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-memcached/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-memcached/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mongodb": {
"version": "0.31.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/mongodb": "3.6.20"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=12.0.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mongodb/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mongodb/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql": {
"version": "0.30.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/mysql": "2.15.19"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql2": {
"version": "0.31.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql2/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-mysql2/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-nestjs-core": {
"version": "0.30.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-nestjs-core/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-nestjs-core/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-net": {
"version": "0.29.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-net/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-net/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pg": {
"version": "0.30.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/pg": "8.6.1",
"@types/pg-pool": "2.0.3"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pg/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pg/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pino": {
"version": "0.30.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"pino": "7.10.0",
"semver": "^7.3.5"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=12.0.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pino/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-pino/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
"node": ">=10"
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
}
},
"node_modules/@opentelemetry/instrumentation-redis": {
"version": "0.32.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/redis": "2.8.31"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-redis-4": {
"version": "0.31.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=12.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-redis-4/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-redis-4/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=10"
}
},
"node_modules/@opentelemetry/instrumentation-redis/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-redis/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-restify": {
"version": "0.29.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/restify": "4.3.8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-restify/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-restify/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-winston": {
"version": "0.29.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation": "^0.29.2"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
}
},
"node_modules/@opentelemetry/instrumentation-winston/node_modules/@opentelemetry/instrumentation": {
"version": "0.29.2",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation-winston/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/instrumentation/node_modules/@opentelemetry/api-metrics": {
"version": "0.30.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=14"
}
},
"node_modules/@opentelemetry/instrumentation/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
"node_modules/@opentelemetry/propagation-utils": {
"version": "0.28.0",
"license": "Apache-2.0",
"engines": {
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"peerDependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/propagator-aws-xray": {
"version": "1.1.0",
"license": "Apache-2.0",
"dependencies": {
"@opentelemetry/core": "^1.0.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/propagator-ot-trace": {
"version": "0.26.0",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/resources": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/resources/node_modules/@opentelemetry/core": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/sdk-trace-base": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "1.3.1",
"@opentelemetry/resources": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/sdk-trace-base/node_modules/@opentelemetry/core": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
},
"peerDependencies": {
"@opentelemetry/api": ">=1.0.0 <1.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@opentelemetry/semantic-conventions": {
"version": "1.3.1",
"license": "Apache-2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.12.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@sideway/address": {
"version": "4.1.4",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "^9.0.0"
}
},
"node_modules/@sideway/formula": {
"version": "3.0.0",
"license": "BSD-3-Clause"
},
"node_modules/@sideway/pinpoint": {
"version": "2.0.0",
"license": "BSD-3-Clause"
},
"node_modules/@sindresorhus/is": {
"version": "0.14.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@szmarczak/http-timer": {
"version": "1.1.2",
"dev": true,
"license": "MIT",
"dependencies": {
"defer-to-connect": "^1.0.1"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/accepts": {
"version": "1.3.5",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/amqplib": {
"version": "0.5.17",
"license": "MIT",
"dependencies": {
"@types/bluebird": "*",
"@types/node": "*"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/aws-lambda": {
"version": "8.10.81",
"license": "MIT"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/bluebird": {
"version": "3.5.36",
"license": "MIT"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/body-parser": {
"version": "1.19.2",
"license": "MIT",
"dependencies": {
"@types/connect": "*",
"@types/node": "*"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/bson": {
"version": "4.2.0",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bson": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/bunyan": {
"version": "1.8.7",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/connect": {
"version": "3.4.35",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/content-disposition": {
"version": "0.5.5",
"license": "MIT"
},
"node_modules/@types/cookies": {
"version": "0.7.7",
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/connect": "*",
"@types/express": "*",
"@types/keygrip": "*",
"@types/node": "*"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/express": {
"version": "4.17.13",
"license": "MIT",
"dependencies": {
"@types/body-parser": "*",
"@types/express-serve-static-core": "^4.17.18",
"@types/qs": "*",
"@types/serve-static": "*"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/express-serve-static-core": {
"version": "4.17.29",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*",
"@types/qs": "*",
"@types/range-parser": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/generic-pool": {
"version": "3.1.10",
"license": "MIT",
"dependencies": {
"@types/node": "*"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/hapi__catbox": {
"version": "10.2.4",
"license": "MIT"
},
"node_modules/@types/hapi__hapi": {
"version": "20.0.9",
"license": "MIT",
"dependencies": {
"@hapi/boom": "^9.0.0",
"@hapi/iron": "^6.0.0",
"@hapi/podium": "^4.1.3",
"@types/hapi__catbox": "*",
"@types/hapi__mimos": "*",
"@types/hapi__shot": "*",
"@types/node": "*",
"joi": "^17.3.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/hapi__mimos": {
"version": "4.1.4",
"license": "MIT",
"dependencies": {
"@types/mime-db": "*"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/hapi__shot": {
"version": "4.1.2",
"license": "MIT",
"dependencies": {
"@types/node": "*"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/http-assert": {
"version": "1.5.3",
"license": "MIT"
},
"node_modules/@types/http-errors": {
"version": "1.8.2",
"license": "MIT"
},
"node_modules/@types/ioredis": {
"version": "4.26.6",
"license": "MIT",
"dependencies": {
"@types/node": "*"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/keygrip": {
"version": "1.0.2",
"license": "MIT"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/koa": {
"version": "2.13.4",
"license": "MIT",
"dependencies": {
"@types/accepts": "*",
"@types/content-disposition": "*",
"@types/cookies": "*",
"@types/http-assert": "*",
"@types/http-errors": "*",
"@types/keygrip": "*",
"@types/koa-compose": "*",
"@types/node": "*"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/koa__router": {
"version": "8.0.7",
"license": "MIT",
"dependencies": {
"@types/koa": "*"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/koa-compose": {
"version": "3.2.5",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/koa": "*"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/memcached": {
"version": "2.2.7",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/mime": {
"version": "1.3.2",
"license": "MIT"
},
"node_modules/@types/mime-db": {
"version": "1.43.1",
"license": "MIT"
},
"node_modules/@types/mongodb": {
"version": "3.6.20",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/bson": "*",
"@types/node": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/mysql": {
"version": "2.15.19",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/node": {
"version": "18.0.0",
"license": "MIT"
},
"node_modules/@types/pg": {
"version": "8.6.1",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/node": "*",
"pg-protocol": "*",
"pg-types": "^2.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/pg-pool": {
"version": "2.0.3",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/pg": "*"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/qs": {
"version": "6.9.7",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/range-parser": {
"version": "1.2.4",
"license": "MIT"
},
"node_modules/@types/redis": {
"version": "2.8.31",
"license": "MIT",
"dependencies": {
"@types/node": "*"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/restify": {
"version": "4.3.8",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/bunyan": "*",
"@types/node": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@types/serve-static": {
"version": "1.13.10",
"license": "MIT",
"dependencies": {
"@types/mime": "^1",
"@types/node": "*"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/@ungap/promise-all-settled": {
"version": "1.1.2",
"dev": true,
"license": "ISC"
},
"node_modules/abbrev": {
"version": "1.1.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC"
},
"node_modules/abstract-logging": {
"version": "2.0.1",
"license": "MIT"
},
"node_modules/accepts": {
"version": "1.3.8",
"license": "MIT",
"dependencies": {
"mime-types": "~2.1.34",
"negotiator": "0.6.3"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/acorn": {
"version": "8.7.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"bin": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/acorn-jsx": {
"version": "5.3.2",
"dev": true,
"license": "MIT",
"peerDependencies": {
"acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ajv": {
"version": "6.12.6",
"license": "MIT",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/another-json": {
"version": "0.2.0",
"license": "Apache-2.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ansi-align": {
"version": "3.0.1",
"dev": true,
"license": "ISC",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"string-width": "^4.1.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ansi-color": {
"version": "0.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ansi-colors": {
"version": "4.1.1",
"dev": true,
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ansi-regex": {
"version": "5.0.1",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ansi-styles": {
"version": "4.3.0",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"color-convert": "^2.0.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/chalk/ansi-styles?sponsor=1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/anymatch": {
"version": "3.1.2",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC",
"dependencies": {
"normalize-path": "^3.0.0",
"picomatch": "^2.0.4"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/archy": {
"version": "1.0.0",
"license": "MIT"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/argparse": {
"version": "2.0.1",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Python-2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/array-flatten": {
"version": "1.1.1",
"license": "MIT"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/async": {
"version": "1.5.2",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/atomic-sleep": {
"version": "1.0.0",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/avvio": {
"version": "7.2.5",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"archy": "^1.0.0",
"debug": "^4.0.0",
"fastq": "^1.6.1",
"queue-microtask": "^1.1.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/avvio/node_modules/debug": {
"version": "4.3.4",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ms": "2.1.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=6.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/avvio/node_modules/ms": {
"version": "2.1.2",
"license": "MIT"
},
"node_modules/balanced-match": {
"version": "1.0.2",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/base64-arraybuffer": {
"version": "0.2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/base64-js": {
"version": "1.5.1",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"license": "MIT"
},
"node_modules/binary-extensions": {
"version": "2.2.0",
"dev": true,
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
"node": ">=8"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/body-parser": {
"version": "1.19.1",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bytes": "3.1.1",
"content-type": "~1.0.4",
"debug": "2.6.9",
"depd": "~1.1.2",
"http-errors": "1.8.1",
"iconv-lite": "0.4.24",
"on-finished": "~2.3.0",
"qs": "6.9.6",
"raw-body": "2.4.2",
"type-is": "~1.6.18"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/boolbase": {
"version": "1.0.0",
"license": "ISC"
},
"node_modules/boxen": {
"version": "5.1.2",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ansi-align": "^3.0.0",
"camelcase": "^6.2.0",
"chalk": "^4.1.0",
"cli-boxes": "^2.2.1",
"string-width": "^4.2.2",
"type-fest": "^0.20.2",
"widest-line": "^3.1.0",
"wrap-ansi": "^7.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/brace-expansion": {
"version": "1.1.11",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/braces": {
"version": "3.0.2",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"fill-range": "^7.0.1"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/browser-stdout": {
"version": "1.3.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/bson": {
"version": "4.6.4",
"license": "Apache-2.0",
"dependencies": {
"buffer": "^5.6.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6.9.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/buffer": {
"version": "5.7.1",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"license": "MIT",
"dependencies": {
"base64-js": "^1.3.1",
"ieee754": "^1.1.13"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/bufrw": {
"version": "1.3.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ansi-color": "^0.2.1",
"error": "^7.0.0",
"hexer": "^1.5.0",
"xtend": "^4.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">= 0.10.x"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/bytes": {
"version": "3.1.1",
"license": "MIT",
"engines": {
"node": ">= 0.8"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cacheable-request": {
"version": "6.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"clone-response": "^1.0.2",
"get-stream": "^5.1.0",
"http-cache-semantics": "^4.0.0",
"keyv": "^3.0.0",
"lowercase-keys": "^2.0.0",
"normalize-url": "^4.1.0",
"responselike": "^1.0.2"
},
"engines": {
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cacheable-request/node_modules/get-stream": {
"version": "5.2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"pump": "^3.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
"node": ">=8"
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cacheable-request/node_modules/lowercase-keys": {
"version": "2.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/callsites": {
"version": "3.1.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/camelcase": {
"version": "6.3.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/chalk": {
"version": "4.1.2",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"engines": {
"node": ">=10"
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/chalk/chalk?sponsor=1"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/chokidar": {
"version": "3.5.3",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"funding": [
{
"type": "individual",
"url": "https://paulmillr.com/funding/"
}
],
"license": "MIT",
"dependencies": {
"anymatch": "~3.1.2",
"braces": "~3.0.2",
"glob-parent": "~5.1.2",
"is-binary-path": "~2.1.0",
"is-glob": "~4.0.1",
"normalize-path": "~3.0.0",
"readdirp": "~3.6.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 8.10.0"
},
"optionalDependencies": {
"fsevents": "~2.3.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/chokidar/node_modules/glob-parent": {
"version": "5.1.2",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"is-glob": "^4.0.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ci-info": {
"version": "2.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/cli-boxes": {
"version": "2.2.1",
"dev": true,
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cliui": {
"version": "7.0.4",
"license": "ISC",
"dependencies": {
"string-width": "^4.2.0",
"strip-ansi": "^6.0.0",
"wrap-ansi": "^7.0.0"
}
Add custom RightPanel support
2022-02-10 01:21:49 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/clone-response": {
"version": "1.0.2",
"dev": true,
"license": "MIT",
"dependencies": {
"mimic-response": "^1.0.0"
}
},
"node_modules/color-convert": {
"version": "2.0.1",
"license": "MIT",
"dependencies": {
"color-name": "~1.1.4"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=7.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/color-name": {
"version": "1.1.4",
"license": "MIT"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/concat-map": {
"version": "0.0.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/configstore": {
"version": "5.0.1",
"dev": true,
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"dot-prop": "^5.2.0",
"graceful-fs": "^4.1.2",
"make-dir": "^3.0.0",
"unique-string": "^2.0.0",
"write-file-atomic": "^3.0.0",
"xdg-basedir": "^4.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/content-disposition": {
"version": "0.5.4",
"license": "MIT",
"dependencies": {
"safe-buffer": "5.2.1"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
"node": ">= 0.6"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/content-type": {
"version": "1.0.4",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cookie": {
"version": "0.4.1",
"license": "MIT",
"engines": {
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"node": ">= 0.6"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cookie-signature": {
"version": "1.0.6",
"license": "MIT"
},
"node_modules/core-js": {
"version": "3.23.1",
"hasInstallScript": true,
"license": "MIT",
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/core-js"
}
},
"node_modules/cross-spawn": {
"version": "7.0.3",
"dev": true,
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 8"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/crypto-random-string": {
"version": "2.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/css-select": {
"version": "4.2.1",
"license": "BSD-2-Clause",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"boolbase": "^1.0.0",
"css-what": "^5.1.0",
"domhandler": "^4.3.0",
"domutils": "^2.8.0",
"nth-check": "^2.0.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"funding": {
"url": "https://github.com/sponsors/fb55"
}
},
"node_modules/css-what": {
"version": "5.1.0",
"license": "BSD-2-Clause",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 6"
},
"funding": {
"url": "https://github.com/sponsors/fb55"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/cssom": {
"version": "0.5.0",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/debug": {
"version": "2.6.9",
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ms": "2.0.0"
}
},
"node_modules/decamelize": {
"version": "4.0.0",
"dev": true,
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/sponsors/sindresorhus"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/decompress-response": {
"version": "3.3.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"mimic-response": "^1.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=4"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/deep-extend": {
"version": "0.6.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=4.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/deep-is": {
"version": "0.1.4",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/deepmerge": {
"version": "4.2.2",
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=0.10.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/defer-to-connect": {
"version": "1.1.3",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/depd": {
"version": "1.1.2",
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/destroy": {
"version": "1.0.4",
"license": "MIT"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/diff": {
"version": "5.0.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-3-Clause",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=0.3.1"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/doctrine": {
"version": "3.0.0",
"dev": true,
"license": "Apache-2.0",
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"esutils": "^2.0.2"
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6.0.0"
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/dom-serializer": {
"version": "1.3.2",
"license": "MIT",
"dependencies": {
"domelementtype": "^2.0.1",
"domhandler": "^4.2.0",
"entities": "^2.0.0"
},
"funding": {
"url": "https://github.com/cheeriojs/dom-serializer?sponsor=1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/domelementtype": {
"version": "2.2.0",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
],
"license": "BSD-2-Clause"
},
"node_modules/domhandler": {
"version": "4.3.0",
"license": "BSD-2-Clause",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"domelementtype": "^2.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 4"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"funding": {
"url": "https://github.com/fb55/domhandler?sponsor=1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/dompurify": {
"version": "2.3.9",
"license": "(MPL-2.0 OR Apache-2.0)"
},
"node_modules/domutils": {
"version": "2.8.0",
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"dom-serializer": "^1.0.1",
"domelementtype": "^2.2.0",
"domhandler": "^4.2.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/fb55/domutils?sponsor=1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/dot-prop": {
"version": "5.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"is-obj": "^2.0.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/duplexer3": {
"version": "0.1.4",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-3-Clause"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/duplexify": {
"version": "4.1.2",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"end-of-stream": "^1.4.1",
"inherits": "^2.0.3",
"readable-stream": "^3.1.1",
"stream-shift": "^1.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ee-first": {
"version": "1.1.1",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/emoji-regex": {
"version": "8.0.0",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/encodeurl": {
"version": "1.0.2",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/end-of-stream": {
"version": "1.4.4",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"once": "^1.4.0"
}
},
"node_modules/entities": {
"version": "2.2.0",
"license": "BSD-2-Clause",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/fb55/entities?sponsor=1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/error": {
"version": "7.0.2",
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"string-template": "~0.2.1",
"xtend": "~4.0.0"
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/esbuild": {
"version": "0.14.31",
"dev": true,
"hasInstallScript": true,
"license": "MIT",
"bin": {
"esbuild": "bin/esbuild"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=12"
},
"optionalDependencies": {
"esbuild-android-64": "0.14.31",
"esbuild-android-arm64": "0.14.31",
"esbuild-darwin-64": "0.14.31",
"esbuild-darwin-arm64": "0.14.31",
"esbuild-freebsd-64": "0.14.31",
"esbuild-freebsd-arm64": "0.14.31",
"esbuild-linux-32": "0.14.31",
"esbuild-linux-64": "0.14.31",
"esbuild-linux-arm": "0.14.31",
"esbuild-linux-arm64": "0.14.31",
"esbuild-linux-mips64le": "0.14.31",
"esbuild-linux-ppc64le": "0.14.31",
"esbuild-linux-riscv64": "0.14.31",
"esbuild-linux-s390x": "0.14.31",
"esbuild-netbsd-64": "0.14.31",
"esbuild-openbsd-64": "0.14.31",
"esbuild-sunos-64": "0.14.31",
"esbuild-windows-32": "0.14.31",
"esbuild-windows-64": "0.14.31",
"esbuild-windows-arm64": "0.14.31"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/esbuild-windows-64": {
"version": "0.14.31",
"cpu": [
"x64"
],
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"optional": true,
"os": [
"win32"
],
"engines": {
"node": ">=12"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/escalade": {
"version": "3.1.1",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/escape-goat": {
"version": "2.1.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/escape-html": {
"version": "1.0.3",
"license": "MIT"
},
"node_modules/escape-string-regexp": {
"version": "4.0.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint": {
"version": "8.8.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@eslint/eslintrc": "^1.0.5",
"@humanwhocodes/config-array": "^0.9.2",
"ajv": "^6.10.0",
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
"debug": "^4.3.2",
"doctrine": "^3.0.0",
"escape-string-regexp": "^4.0.0",
"eslint-scope": "^7.1.0",
"eslint-utils": "^3.0.0",
"eslint-visitor-keys": "^3.2.0",
"espree": "^9.3.0",
"esquery": "^1.4.0",
"esutils": "^2.0.2",
"fast-deep-equal": "^3.1.3",
"file-entry-cache": "^6.0.1",
"functional-red-black-tree": "^1.0.1",
"glob-parent": "^6.0.1",
"globals": "^13.6.0",
"ignore": "^5.2.0",
"import-fresh": "^3.0.0",
"imurmurhash": "^0.1.4",
"is-glob": "^4.0.0",
"js-yaml": "^4.1.0",
"json-stable-stringify-without-jsonify": "^1.0.1",
"levn": "^0.4.1",
"lodash.merge": "^4.6.2",
"minimatch": "^3.0.4",
"natural-compare": "^1.4.0",
"optionator": "^0.9.1",
"regexpp": "^3.2.0",
"strip-ansi": "^6.0.1",
"strip-json-comments": "^3.1.0",
"text-table": "^0.2.0",
"v8-compile-cache": "^2.0.3"
},
"bin": {
"eslint": "bin/eslint.js"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://opencollective.com/eslint"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-config-prettier": {
"version": "8.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"bin": {
"eslint-config-prettier": "bin/cli.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"eslint": ">=7.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-es": {
"version": "3.0.1",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"eslint-utils": "^2.0.0",
"regexpp": "^3.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.10.0"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
},
"peerDependencies": {
"eslint": ">=4.19.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-es/node_modules/eslint-utils": {
"version": "2.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"eslint-visitor-keys": "^1.1.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-es/node_modules/eslint-visitor-keys": {
"version": "1.3.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Apache-2.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=4"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-node": {
"version": "11.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"eslint-plugin-es": "^3.0.0",
"eslint-utils": "^2.0.0",
"ignore": "^5.1.1",
"minimatch": "^3.0.4",
"resolve": "^1.10.1",
"semver": "^6.1.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.10.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"eslint": ">=5.16.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-node/node_modules/eslint-utils": {
"version": "2.1.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"eslint-visitor-keys": "^1.1.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-node/node_modules/eslint-visitor-keys": {
"version": "1.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Apache-2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
"node": ">=4"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-plugin-prettier": {
"version": "4.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"prettier-linter-helpers": "^1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
"node": ">=6.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"peerDependencies": {
"eslint": ">=7.28.0",
"prettier": ">=2.0.0"
},
"peerDependenciesMeta": {
"eslint-config-prettier": {
"optional": true
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-scope": {
"version": "7.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"esrecurse": "^4.3.0",
"estraverse": "^5.2.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-utils": {
"version": "3.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"eslint-visitor-keys": "^2.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^10.0.0 || ^12.0.0 || >= 14.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/sponsors/mysticatea"
},
"peerDependencies": {
"eslint": ">=5"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-utils/node_modules/eslint-visitor-keys": {
WIP: start of tests
2022-02-22 15:06:29 -07:00
"version": "2.1.0",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint-visitor-keys": {
"version": "3.2.0",
"dev": true,
"license": "Apache-2.0",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint/node_modules/debug": {
"version": "4.3.3",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ms": "2.1.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/eslint/node_modules/ms": {
"version": "2.1.2",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/espree": {
"version": "9.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"acorn": "^8.7.0",
"acorn-jsx": "^5.3.1",
"eslint-visitor-keys": "^3.1.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/esquery": {
"version": "1.4.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-3-Clause",
"dependencies": {
"estraverse": "^5.1.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">=0.10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/esrecurse": {
"version": "4.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"estraverse": "^5.2.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=4.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/estraverse": {
"version": "5.3.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=4.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/esutils": {
"version": "2.0.3",
"dev": true,
"license": "BSD-2-Clause",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=0.10.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/etag": {
"version": "1.8.1",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/express": {
"version": "4.17.2",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"accepts": "~1.3.7",
"array-flatten": "1.1.1",
"body-parser": "1.19.1",
"content-disposition": "0.5.4",
"content-type": "~1.0.4",
"cookie": "0.4.1",
"cookie-signature": "1.0.6",
"debug": "2.6.9",
"depd": "~1.1.2",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"finalhandler": "~1.1.2",
"fresh": "0.5.2",
"merge-descriptors": "1.0.1",
"methods": "~1.1.2",
"on-finished": "~2.3.0",
"parseurl": "~1.3.3",
"path-to-regexp": "0.1.7",
"proxy-addr": "~2.0.7",
"qs": "6.9.6",
"range-parser": "~1.2.1",
"safe-buffer": "5.2.1",
"send": "0.17.2",
"serve-static": "1.14.2",
"setprototypeof": "1.2.0",
"statuses": "~1.5.0",
"type-is": "~1.6.18",
"utils-merge": "1.0.1",
"vary": "~1.1.2"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"engines": {
"node": ">= 0.10.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fast-decode-uri-component": {
"version": "1.0.1",
"license": "MIT"
},
"node_modules/fast-deep-equal": {
"version": "3.1.3",
"license": "MIT"
},
"node_modules/fast-diff": {
"version": "1.2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "Apache-2.0"
},
"node_modules/fast-json-stable-stringify": {
"version": "2.1.0",
"license": "MIT"
},
"node_modules/fast-json-stringify": {
"version": "2.7.13",
"license": "MIT",
"dependencies": {
"ajv": "^6.11.0",
"deepmerge": "^4.2.2",
"rfdc": "^1.2.0",
"string-similarity": "^4.0.1"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 10.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fast-levenshtein": {
"version": "2.0.6",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/fast-redact": {
"version": "3.1.1",
"license": "MIT",
"engines": {
"node": ">=6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fast-safe-stringify": {
"version": "2.1.1",
"license": "MIT"
},
"node_modules/fastify": {
"version": "3.29.0",
"license": "MIT",
"dependencies": {
"@fastify/ajv-compiler": "^1.0.0",
"@fastify/error": "^2.0.0",
"abstract-logging": "^2.0.0",
"avvio": "^7.1.2",
"fast-json-stringify": "^2.5.2",
"find-my-way": "^4.5.0",
"flatstr": "^1.0.12",
"light-my-request": "^4.2.0",
"pino": "^6.13.0",
"process-warning": "^1.0.0",
"proxy-addr": "^2.0.7",
"rfdc": "^1.1.4",
"secure-json-parse": "^2.0.0",
"semver": "^7.3.2",
"tiny-lru": "^8.0.1"
}
},
"node_modules/fastify/node_modules/pino": {
"version": "6.14.0",
"license": "MIT",
"dependencies": {
"fast-redact": "^3.0.0",
"fast-safe-stringify": "^2.0.8",
"flatstr": "^1.0.12",
"pino-std-serializers": "^3.1.0",
"process-warning": "^1.0.0",
"quick-format-unescaped": "^4.0.3",
"sonic-boom": "^1.0.2"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"bin": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"pino": "bin.js"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fastify/node_modules/pino-std-serializers": {
"version": "3.2.0",
"license": "MIT"
},
"node_modules/fastify/node_modules/semver": {
"version": "7.3.7",
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"bin": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver": "bin/semver.js"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fastify/node_modules/sonic-boom": {
"version": "1.4.1",
"license": "MIT",
"dependencies": {
"atomic-sleep": "^1.0.0",
"flatstr": "^1.0.12"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fastq": {
"version": "1.13.0",
"license": "ISC",
"dependencies": {
"reusify": "^1.0.4"
}
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/file-entry-cache": {
"version": "6.0.1",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"flat-cache": "^3.0.4"
},
"engines": {
"node": "^10.12.0 || >=12.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fill-range": {
"version": "7.0.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"to-regex-range": "^5.0.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
"node": ">=8"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/finalhandler": {
"version": "1.1.2",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
"debug": "2.6.9",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"on-finished": "~2.3.0",
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"parseurl": "~1.3.3",
"statuses": "~1.5.0",
"unpipe": "~1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.8"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/find-my-way": {
"version": "4.5.1",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"fast-decode-uri-component": "^1.0.1",
"fast-deep-equal": "^3.1.3",
"safe-regex2": "^2.0.0",
"semver-store": "^0.3.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/find-up": {
"version": "5.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"locate-path": "^6.0.0",
"path-exists": "^4.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/flat": {
"version": "5.0.2",
"dev": true,
"license": "BSD-3-Clause",
"bin": {
"flat": "cli.js"
}
},
"node_modules/flat-cache": {
"version": "3.0.4",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"flatted": "^3.1.0",
"rimraf": "^3.0.2"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "^10.12.0 || >=12.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/flatstr": {
"version": "1.0.12",
"license": "MIT"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/flatted": {
"version": "3.2.5",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC"
},
"node_modules/forwarded": {
"version": "0.2.0",
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fresh": {
"version": "0.5.2",
"license": "MIT",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"engines": {
"node": ">= 0.6"
Federated homeservers in Docker for e2e tests
2022-02-22 19:25:24 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/fs.realpath": {
"version": "1.0.0",
"dev": true,
"license": "ISC"
},
"node_modules/function-bind": {
"version": "1.1.1",
"license": "MIT"
},
"node_modules/functional-red-black-tree": {
"version": "1.0.1",
"dev": true,
"license": "MIT"
},
"node_modules/get-caller-file": {
"version": "2.0.5",
"license": "ISC",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": "6.* || 8.* || >= 10.*"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/get-stream": {
"version": "4.1.0",
"dev": true,
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"pump": "^3.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/glob": {
"version": "7.2.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC",
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/glob-parent": {
"version": "6.0.2",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"is-glob": "^4.0.3"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10.13.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/global-dirs": {
"version": "3.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"ini": "2.0.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=10"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/sponsors/sindresorhus"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/globals": {
"version": "13.12.1",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"type-fest": "^0.20.2"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/got": {
"version": "9.6.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@sindresorhus/is": "^0.14.0",
"@szmarczak/http-timer": "^1.1.2",
"cacheable-request": "^6.0.0",
"decompress-response": "^3.3.0",
"duplexer3": "^0.1.4",
"get-stream": "^4.1.0",
"lowercase-keys": "^1.0.1",
"mimic-response": "^1.0.1",
"p-cancelable": "^1.0.0",
"to-readable-stream": "^1.0.0",
"url-parse-lax": "^3.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8.6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/graceful-fs": {
"version": "4.2.9",
"dev": true,
"license": "ISC"
},
"node_modules/graphql": {
"version": "15.8.0",
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 10.x"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/growl": {
"version": "1.10.5",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"engines": {
"node": ">=4.x"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/has": {
"version": "1.0.3",
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"function-bind": "^1.1.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.4.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/has-flag": {
"version": "4.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/has-yarn": {
"version": "2.1.0",
"dev": true,
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/he": {
"version": "1.2.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"bin": {
"he": "bin/he"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/hexer": {
"version": "1.5.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ansi-color": "^0.2.1",
"minimist": "^1.1.0",
"process": "^0.10.0",
"xtend": "^4.0.0"
},
"bin": {
"hexer": "cli.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.10.x"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/html-escaper": {
"version": "3.0.3",
"license": "MIT"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/htmlparser2": {
"version": "7.2.0",
"funding": [
"https://github.com/fb55/htmlparser2?sponsor=1",
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
],
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"domelementtype": "^2.0.1",
"domhandler": "^4.2.2",
"domutils": "^2.8.0",
"entities": "^3.0.1"
}
},
"node_modules/htmlparser2/node_modules/entities": {
"version": "3.0.1",
"license": "BSD-2-Clause",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=0.12"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/fb55/entities?sponsor=1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/http-cache-semantics": {
"version": "4.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "BSD-2-Clause"
},
"node_modules/http-errors": {
"version": "1.8.1",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"depd": "~1.1.2",
"inherits": "2.0.4",
"setprototypeof": "1.2.0",
"statuses": ">= 1.5.0 < 2",
"toidentifier": "1.0.1"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 0.6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/hydrogen-view-sdk": {
"name": "@mlm/hydrogen-view-sdk",
Fix missing `room.observePowerLevels()` throwing error after render (#57) Fix missing `room.observePowerLevels()` throwing error after render. ``` Uncaught (in promise) TypeError: this._room.observePowerLevels is not a function at RoomViewModel2._recreateComposerOnPowerLevelChange (matrix-public-archive.js:23498:53) at new RoomViewModel2 (matrix-public-archive.js:23469:14) at mountHydrogen (matrix-public-archive.js:27131:25) at matrix-public-archive.js:27174:1 ``` Doesn't affect main-line rendering but the error is annoying to see. More Hydrogen boilerplate 😞
2022-08-30 22:40:07 -06:00
"version": "0.15.0-scratch",
"resolved": "https://registry.npmjs.org/@mlm/hydrogen-view-sdk/-/hydrogen-view-sdk-0.15.0-scratch.tgz",
"integrity": "sha512-QRsJjk56EdMWWgSEewLOG0FgRPqP8Yyc15fyU+60GzBrSL/fh6jfkgGejLHuJbPYFcKnkPpCTDEbEDLfP2kjaQ==",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@matrix-org/olm": "https://gitlab.matrix.org/api/v4/projects/27/packages/npm/@matrix-org/olm/-/@matrix-org/olm-3.2.8.tgz",
"another-json": "^0.2.0",
"base64-arraybuffer": "^0.2.0",
"dompurify": "^2.3.0",
"off-color": "^2.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/iconv-lite": {
"version": "0.4.24",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"safer-buffer": ">= 2.1.2 < 3"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=0.10.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ieee754": {
"version": "1.2.1",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"license": "BSD-3-Clause"
},
"node_modules/ignore": {
"version": "5.2.0",
"dev": true,
"license": "MIT",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">= 4"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/ignore-by-default": {
"version": "1.0.1",
"dev": true,
"license": "ISC"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/import-fresh": {
"version": "3.3.0",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"parent-module": "^1.0.0",
"resolve-from": "^4.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=6"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/import-lazy": {
"version": "2.1.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/imurmurhash": {
"version": "0.1.4",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.8.19"
}
},
"node_modules/inflight": {
"version": "1.0.6",
"dev": true,
"license": "ISC",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"once": "^1.3.0",
"wrappy": "1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/inherits": {
"version": "2.0.4",
"license": "ISC"
},
"node_modules/ini": {
"version": "2.0.0",
"license": "ISC",
"engines": {
"node": ">=10"
}
},
"node_modules/ipaddr.js": {
"version": "1.9.1",
"license": "MIT",
"engines": {
"node": ">= 0.10"
}
},
"node_modules/is-binary-path": {
"version": "2.1.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"binary-extensions": "^2.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-ci": {
"version": "2.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ci-info": "^2.0.0"
},
"bin": {
"is-ci": "bin.js"
}
},
"node_modules/is-core-module": {
"version": "2.8.1",
"license": "MIT",
"dependencies": {
"has": "^1.0.3"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-extglob": {
"version": "2.1.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"engines": {
"node": ">=8"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-glob": {
"version": "4.0.3",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"is-extglob": "^2.1.1"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"engines": {
"node": ">=0.10.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-installed-globally": {
"version": "0.4.0",
"dev": true,
"license": "MIT",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"global-dirs": "^3.0.0",
"is-path-inside": "^3.0.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"engines": {
"node": ">=10"
},
"funding": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"url": "https://github.com/sponsors/sindresorhus"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-npm": {
"version": "5.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
Add custom RightPanel support
2022-02-10 01:21:49 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-number": {
"version": "7.0.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"engines": {
"node": ">=0.12.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-obj": {
"version": "2.0.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=8"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-path-inside": {
"version": "3.0.3",
"dev": true,
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-plain-obj": {
"version": "2.1.0",
"dev": true,
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node": ">=8"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-typedarray": {
"version": "1.0.0",
"dev": true,
"license": "MIT"
},
"node_modules/is-unicode-supported": {
"version": "0.1.0",
"dev": true,
"license": "MIT",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"engines": {
"node": ">=10"
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
WIP: start of tests
2022-02-22 15:06:29 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/is-yarn-global": {
"version": "0.3.0",
"dev": true,
"license": "MIT"
},
"node_modules/isexe": {
WIP: start of tests
2022-02-22 15:06:29 -07:00
"version": "2.0.0",
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "ISC"
},
"node_modules/jaeger-client": {
"version": "3.19.0",
"license": "Apache-2.0",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node-int64": "^0.4.0",
"opentracing": "^0.14.4",
"thriftrw": "^3.5.0",
"uuid": "^8.3.2",
"xorshift": "^1.1.1"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"engines": {
"node": ">=10"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/joi": {
"version": "17.6.0",
"license": "BSD-3-Clause",
"dependencies": {
"@hapi/hoek": "^9.0.0",
"@hapi/topo": "^5.0.0",
"@sideway/address": "^4.1.3",
"@sideway/formula": "^3.0.0",
"@sideway/pinpoint": "^2.0.0"
}
},
"node_modules/js-yaml": {
"version": "4.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT",
"dependencies": {
"argparse": "^2.0.1"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bin": {
"js-yaml": "bin/js-yaml.js"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/json-buffer": {
"version": "3.0.0",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"license": "MIT"
},
"node_modules/json-schema-traverse": {
"version": "0.4.1",
"license": "MIT"
},
"node_modules/json-stable-stringify-without-jsonify": {
"version": "1.0.1",
"dev": true,
"license": "MIT"
},
Use JSON5 for configuration files with comments (#52) Use JSON5 for configuration files with comments. Now we can leave the available config in `config.default.json` without having to add weird instructions to remove the `xxx`, etc - https://www.npmjs.com/package/json5 - https://www.npmjs.com/package/nconf - https://github.com/indexzero/nconf/issues/113#issuecomment-69999413
2022-08-29 19:33:02 -06:00
"node_modules/json5": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.1.tgz",
"integrity": "sha512-1hqLFMSrGHRHxav9q9gNjJ5EXznIxGVO09xQRrwplcS8qs28pZ8s8hupZAmqDwZUmVZ2Qb2jnyPOWcDH8m8dlA==",
"bin": {
"json5": "lib/cli.js"
},
"engines": {
"node": ">=6"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node_modules/keyv": {
"version": "3.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"json-buffer": "3.0.0"
}
},
"node_modules/latest-version": {
"version": "5.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"package-json": "^6.3.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/levn": {
"version": "0.4.1",
"dev": true,
"license": "MIT",
"dependencies": {
"prelude-ls": "^1.2.1",
"type-check": "~0.4.0"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/light-my-request": {
"version": "4.10.1",
"license": "BSD-3-Clause",
"dependencies": {
"ajv": "^8.1.0",
"cookie": "^0.5.0",
"process-warning": "^1.0.0",
"set-cookie-parser": "^2.4.1"
}
},
"node_modules/light-my-request/node_modules/ajv": {
"version": "8.11.0",
"license": "MIT",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/light-my-request/node_modules/cookie": {
"version": "0.5.0",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/light-my-request/node_modules/json-schema-traverse": {
"version": "1.0.0",
"license": "MIT"
},
"node_modules/linkedom": {
"version": "0.14.1",
"license": "ISC",
"dependencies": {
"css-select": "^4.2.1",
"cssom": "^0.5.0",
"html-escaper": "^3.0.3",
"htmlparser2": "^7.2.0",
"uhyphen": "^0.1.0"
}
},
"node_modules/locate-path": {
"version": "6.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"p-locate": "^5.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/lodash.merge": {
"version": "4.6.2",
"dev": true,
"license": "MIT"
},
"node_modules/log-symbols": {
"version": "4.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"chalk": "^4.1.0",
"is-unicode-supported": "^0.1.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/long": {
"version": "2.4.0",
"license": "Apache-2.0",
"engines": {
"node": ">=0.6"
}
},
"node_modules/lowercase-keys": {
"version": "1.0.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/lru-cache": {
"version": "6.0.0",
"license": "ISC",
"dependencies": {
"yallist": "^4.0.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/make-dir": {
"version": "3.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"semver": "^6.0.0"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/matrix-public-archive-shared": {
"resolved": "shared",
"link": true
},
"node_modules/media-typer": {
"version": "0.3.0",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/merge-descriptors": {
"version": "1.0.1",
"license": "MIT"
},
"node_modules/merge-options": {
"version": "3.0.4",
"dev": true,
"license": "MIT",
"dependencies": {
"is-plain-obj": "^2.1.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/methods": {
"version": "1.1.2",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mime": {
"version": "1.6.0",
"license": "MIT",
"bin": {
"mime": "cli.js"
},
"engines": {
"node": ">=4"
}
},
"node_modules/mime-db": {
"version": "1.51.0",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mime-types": {
"version": "2.1.34",
"license": "MIT",
"dependencies": {
"mime-db": "1.51.0"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mimic-response": {
"version": "1.0.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/minimatch": {
"version": "3.0.5",
"dev": true,
"license": "ISC",
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/minimist": {
"version": "1.2.6",
"license": "MIT"
},
"node_modules/mocha": {
"version": "9.2.1",
"dev": true,
"license": "MIT",
"dependencies": {
"@ungap/promise-all-settled": "1.1.2",
"ansi-colors": "4.1.1",
"browser-stdout": "1.3.1",
"chokidar": "3.5.3",
"debug": "4.3.3",
"diff": "5.0.0",
"escape-string-regexp": "4.0.0",
"find-up": "5.0.0",
"glob": "7.2.0",
"growl": "1.10.5",
"he": "1.2.0",
"js-yaml": "4.1.0",
"log-symbols": "4.1.0",
"minimatch": "3.0.4",
"ms": "2.1.3",
"nanoid": "3.2.0",
"serialize-javascript": "6.0.0",
"strip-json-comments": "3.1.1",
"supports-color": "8.1.1",
"which": "2.0.2",
"workerpool": "6.2.0",
"yargs": "16.2.0",
"yargs-parser": "20.2.4",
"yargs-unparser": "2.0.0"
},
"bin": {
"_mocha": "bin/_mocha",
"mocha": "bin/mocha"
},
"engines": {
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/mochajs"
}
},
"node_modules/mocha/node_modules/debug": {
"version": "4.3.3",
"dev": true,
"license": "MIT",
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/mocha/node_modules/debug/node_modules/ms": {
"version": "2.1.2",
"dev": true,
"license": "MIT"
},
"node_modules/mocha/node_modules/minimatch": {
"version": "3.0.4",
"dev": true,
"license": "ISC",
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/mocha/node_modules/ms": {
"version": "2.1.3",
"dev": true,
"license": "MIT"
},
"node_modules/mocha/node_modules/nanoid": {
"version": "3.2.0",
"dev": true,
"license": "MIT",
"bin": {
"nanoid": "bin/nanoid.cjs"
},
"engines": {
"node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
}
},
"node_modules/mocha/node_modules/supports-color": {
"version": "8.1.1",
"dev": true,
"license": "MIT",
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/supports-color?sponsor=1"
}
},
"node_modules/module-details-from-path": {
"version": "1.0.3",
"license": "MIT"
},
"node_modules/ms": {
"version": "2.0.0",
"license": "MIT"
},
"node_modules/nanoid": {
"version": "3.3.4",
"dev": true,
"license": "MIT",
"bin": {
"nanoid": "bin/nanoid.cjs"
},
"engines": {
"node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
}
},
"node_modules/natural-compare": {
"version": "1.4.0",
"dev": true,
"license": "MIT"
},
"node_modules/nconf": {
"version": "0.11.3",
"license": "MIT",
"dependencies": {
"async": "^1.4.0",
"ini": "^2.0.0",
"secure-keys": "^1.0.0",
"yargs": "^16.1.1"
},
"engines": {
"node": ">= 0.4.0"
}
},
"node_modules/negotiator": {
"version": "0.6.3",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/node-fetch": {
"version": "2.6.7",
"license": "MIT",
"dependencies": {
"whatwg-url": "^5.0.0"
},
"engines": {
"node": "4.x || >=6.0.0"
},
"peerDependencies": {
"encoding": "^0.1.0"
},
"peerDependenciesMeta": {
"encoding": {
"optional": true
}
}
},
"node_modules/node-int64": {
"version": "0.4.0",
"license": "MIT"
},
"node_modules/nodemon": {
"version": "2.0.15",
"dev": true,
"hasInstallScript": true,
"license": "MIT",
"dependencies": {
"chokidar": "^3.5.2",
"debug": "^3.2.7",
"ignore-by-default": "^1.0.1",
"minimatch": "^3.0.4",
"pstree.remy": "^1.1.8",
"semver": "^5.7.1",
"supports-color": "^5.5.0",
"touch": "^3.1.0",
"undefsafe": "^2.0.5",
"update-notifier": "^5.1.0"
},
"bin": {
"nodemon": "bin/nodemon.js"
},
"engines": {
"node": ">=8.10.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/nodemon"
}
},
"node_modules/nodemon/node_modules/debug": {
"version": "3.2.7",
"dev": true,
"license": "MIT",
"dependencies": {
"ms": "^2.1.1"
}
},
"node_modules/nodemon/node_modules/has-flag": {
"version": "3.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/nodemon/node_modules/ms": {
"version": "2.1.3",
"dev": true,
"license": "MIT"
},
"node_modules/nodemon/node_modules/semver": {
"version": "5.7.1",
"dev": true,
"license": "ISC",
"bin": {
"semver": "bin/semver"
}
},
"node_modules/nodemon/node_modules/supports-color": {
"version": "5.5.0",
"dev": true,
"license": "MIT",
"dependencies": {
"has-flag": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/nopt": {
"version": "1.0.10",
"dev": true,
"license": "MIT",
"dependencies": {
"abbrev": "1"
},
"bin": {
"nopt": "bin/nopt.js"
}
},
"node_modules/normalize-path": {
"version": "3.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/normalize-url": {
"version": "4.5.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
"node_modules/nth-check": {
"version": "2.0.1",
"license": "BSD-2-Clause",
"dependencies": {
"boolbase": "^1.0.0"
},
"funding": {
"url": "https://github.com/fb55/nth-check?sponsor=1"
}
},
"node_modules/off-color": {
"version": "2.0.0",
"license": "MIT",
"dependencies": {
"core-js": "^3.6.5"
}
},
"node_modules/on-exit-leak-free": {
"version": "0.2.0",
"license": "MIT"
},
"node_modules/on-finished": {
"version": "2.3.0",
"license": "MIT",
"dependencies": {
"ee-first": "1.1.1"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/once": {
"version": "1.4.0",
"license": "ISC",
"dependencies": {
"wrappy": "1"
}
},
"node_modules/opentracing": {
"version": "0.14.7",
"license": "Apache-2.0",
"engines": {
"node": ">=0.10"
}
},
"node_modules/optionator": {
"version": "0.9.1",
"dev": true,
"license": "MIT",
"dependencies": {
"deep-is": "^0.1.3",
"fast-levenshtein": "^2.0.6",
"levn": "^0.4.1",
"prelude-ls": "^1.2.1",
"type-check": "^0.4.0",
"word-wrap": "^1.2.3"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/p-cancelable": {
"version": "1.1.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/p-limit": {
"version": "3.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"yocto-queue": "^0.1.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/p-locate": {
"version": "5.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"p-limit": "^3.0.2"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/package-json": {
"version": "6.5.0",
"dev": true,
"license": "MIT",
"dependencies": {
"got": "^9.6.0",
"registry-auth-token": "^4.0.0",
"registry-url": "^5.0.0",
"semver": "^6.2.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/parent-module": {
"version": "1.0.1",
"dev": true,
"license": "MIT",
"dependencies": {
"callsites": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/parseurl": {
"version": "1.3.3",
"license": "MIT",
"engines": {
"node": ">= 0.8"
}
},
"node_modules/path-exists": {
"version": "4.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
"node_modules/path-is-absolute": {
"version": "1.0.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-key": {
"version": "3.1.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
"node_modules/path-parse": {
"version": "1.0.7",
"license": "MIT"
},
"node_modules/path-to-regexp": {
"version": "0.1.7",
"license": "MIT"
},
"node_modules/pg-int8": {
"version": "1.0.1",
"license": "ISC",
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/pg-protocol": {
"version": "1.5.0",
"license": "MIT"
},
"node_modules/pg-types": {
"version": "2.2.0",
"license": "MIT",
"dependencies": {
"pg-int8": "1.0.1",
"postgres-array": "~2.0.0",
"postgres-bytea": "~1.0.0",
"postgres-date": "~1.0.4",
"postgres-interval": "^1.1.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/picocolors": {
"version": "1.0.0",
"dev": true,
"license": "ISC"
},
"node_modules/picomatch": {
"version": "2.3.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8.6"
},
"funding": {
"url": "https://github.com/sponsors/jonschlinkert"
}
},
"node_modules/pino": {
"version": "7.10.0",
"license": "MIT",
"dependencies": {
"atomic-sleep": "^1.0.0",
"fast-redact": "^3.0.0",
"on-exit-leak-free": "^0.2.0",
"pino-abstract-transport": "v0.5.0",
"pino-std-serializers": "^4.0.0",
"process-warning": "^1.0.0",
"quick-format-unescaped": "^4.0.3",
"real-require": "^0.1.0",
"safe-stable-stringify": "^2.1.0",
"sonic-boom": "^2.2.1",
"thread-stream": "^0.15.1"
},
"bin": {
"pino": "bin.js"
}
},
"node_modules/pino-abstract-transport": {
"version": "0.5.0",
"license": "MIT",
"dependencies": {
"duplexify": "^4.1.2",
"split2": "^4.0.0"
}
},
"node_modules/pino-std-serializers": {
"version": "4.0.0",
"license": "MIT"
},
"node_modules/postcss": {
"version": "8.4.14",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
}
],
"license": "MIT",
"dependencies": {
"nanoid": "^3.3.4",
"picocolors": "^1.0.0",
"source-map-js": "^1.0.2"
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
"node_modules/postgres-array": {
"version": "2.0.0",
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/postgres-bytea": {
"version": "1.0.0",
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/postgres-date": {
"version": "1.0.7",
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/postgres-interval": {
"version": "1.2.0",
"license": "MIT",
"dependencies": {
"xtend": "^4.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/prelude-ls": {
"version": "1.2.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/prepend-http": {
"version": "2.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/prettier": {
"version": "2.5.1",
"dev": true,
"license": "MIT",
"bin": {
"prettier": "bin-prettier.js"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/prettier-linter-helpers": {
"version": "1.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"fast-diff": "^1.1.2"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/process": {
"version": "0.10.1",
"engines": {
"node": ">= 0.6.0"
}
},
"node_modules/process-warning": {
"version": "1.0.0",
"license": "MIT"
},
"node_modules/proxy-addr": {
"version": "2.0.7",
"license": "MIT",
"dependencies": {
"forwarded": "0.2.0",
"ipaddr.js": "1.9.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/pstree.remy": {
"version": "1.1.8",
"dev": true,
"license": "MIT"
},
"node_modules/pump": {
"version": "3.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/punycode": {
"version": "2.1.1",
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/pupa": {
"version": "2.1.1",
"dev": true,
"license": "MIT",
"dependencies": {
"escape-goat": "^2.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/qs": {
"version": "6.9.6",
"license": "BSD-3-Clause",
"engines": {
"node": ">=0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/queue-microtask": {
"version": "1.2.3",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"license": "MIT"
},
"node_modules/quick-format-unescaped": {
"version": "4.0.4",
"license": "MIT"
},
"node_modules/randombytes": {
"version": "2.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "^5.1.0"
}
},
"node_modules/range-parser": {
"version": "1.2.1",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/raw-body": {
"version": "2.4.2",
"license": "MIT",
"dependencies": {
"bytes": "3.1.1",
"http-errors": "1.8.1",
"iconv-lite": "0.4.24",
"unpipe": "1.0.0"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/rc": {
"version": "1.2.8",
"dev": true,
"license": "(BSD-2-Clause OR MIT OR Apache-2.0)",
"dependencies": {
"deep-extend": "^0.6.0",
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
},
"bin": {
"rc": "cli.js"
}
},
"node_modules/rc/node_modules/ini": {
"version": "1.3.8",
"dev": true,
"license": "ISC"
},
"node_modules/rc/node_modules/strip-json-comments": {
"version": "2.0.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/readable-stream": {
"version": "3.6.0",
"license": "MIT",
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/readdirp": {
"version": "3.6.0",
"dev": true,
"license": "MIT",
"dependencies": {
"picomatch": "^2.2.1"
},
"engines": {
"node": ">=8.10.0"
}
},
"node_modules/real-require": {
"version": "0.1.0",
"license": "MIT",
"engines": {
"node": ">= 12.13.0"
}
},
"node_modules/regexpp": {
"version": "3.2.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
}
},
"node_modules/registry-auth-token": {
"version": "4.2.1",
"dev": true,
"license": "MIT",
"dependencies": {
"rc": "^1.2.8"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/registry-url": {
"version": "5.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"rc": "^1.2.8"
},
"engines": {
"node": ">=8"
}
},
"node_modules/require-directory": {
"version": "2.1.1",
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/require-from-string": {
"version": "2.0.2",
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/require-in-the-middle": {
"version": "5.1.0",
"license": "MIT",
"dependencies": {
"debug": "^4.1.1",
"module-details-from-path": "^1.0.3",
"resolve": "^1.12.0"
}
},
"node_modules/require-in-the-middle/node_modules/debug": {
"version": "4.3.4",
"license": "MIT",
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/require-in-the-middle/node_modules/ms": {
"version": "2.1.2",
"license": "MIT"
},
"node_modules/resolve": {
"version": "1.22.0",
"license": "MIT",
"dependencies": {
"is-core-module": "^2.8.1",
"path-parse": "^1.0.7",
"supports-preserve-symlinks-flag": "^1.0.0"
},
"bin": {
"resolve": "bin/resolve"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/resolve-from": {
"version": "4.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/responselike": {
"version": "1.0.2",
"dev": true,
"license": "MIT",
"dependencies": {
"lowercase-keys": "^1.0.0"
}
},
"node_modules/ret": {
"version": "0.2.2",
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/reusify": {
"version": "1.0.4",
"license": "MIT",
"engines": {
"iojs": ">=1.0.0",
"node": ">=0.10.0"
}
},
"node_modules/rfdc": {
"version": "1.3.0",
"license": "MIT"
},
"node_modules/rimraf": {
"version": "3.0.2",
"dev": true,
"license": "ISC",
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/rollup": {
"version": "2.67.2",
"dev": true,
"license": "MIT",
"bin": {
"rollup": "dist/bin/rollup"
},
"engines": {
"node": ">=10.0.0"
},
"optionalDependencies": {
"fsevents": "~2.3.2"
}
},
"node_modules/safe-buffer": {
"version": "5.2.1",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"license": "MIT"
},
"node_modules/safe-regex2": {
"version": "2.0.0",
"license": "MIT",
"dependencies": {
"ret": "~0.2.0"
}
},
"node_modules/safe-stable-stringify": {
"version": "2.3.1",
"license": "MIT",
"engines": {
"node": ">=10"
}
},
"node_modules/safer-buffer": {
"version": "2.1.2",
"license": "MIT"
},
"node_modules/secure-json-parse": {
"version": "2.4.0",
"license": "BSD-3-Clause"
},
"node_modules/secure-keys": {
"version": "1.0.0",
"license": "MIT"
},
"node_modules/semver": {
"version": "6.3.0",
"dev": true,
"license": "ISC",
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/semver-diff": {
"version": "3.1.1",
"dev": true,
"license": "MIT",
"dependencies": {
"semver": "^6.3.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/semver-store": {
"version": "0.3.0",
"license": "MIT"
},
"node_modules/send": {
"version": "0.17.2",
"license": "MIT",
"dependencies": {
"debug": "2.6.9",
"depd": "~1.1.2",
"destroy": "~1.0.4",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"fresh": "0.5.2",
"http-errors": "1.8.1",
"mime": "1.6.0",
"ms": "2.1.3",
"on-finished": "~2.3.0",
"range-parser": "~1.2.1",
"statuses": "~1.5.0"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/send/node_modules/ms": {
"version": "2.1.3",
"license": "MIT"
},
"node_modules/serialize-javascript": {
"version": "6.0.0",
"dev": true,
"license": "BSD-3-Clause",
"dependencies": {
"randombytes": "^2.1.0"
}
},
"node_modules/serve-static": {
"version": "1.14.2",
"license": "MIT",
"dependencies": {
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"parseurl": "~1.3.3",
"send": "0.17.2"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/set-cookie-parser": {
"version": "2.5.0",
"license": "MIT"
},
"node_modules/setprototypeof": {
"version": "1.2.0",
"license": "ISC"
},
"node_modules/shebang-command": {
"version": "2.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"shebang-regex": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/shebang-regex": {
"version": "3.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
"node_modules/shimmer": {
"version": "1.2.1",
"license": "BSD-2-Clause"
},
"node_modules/signal-exit": {
"version": "3.0.7",
"dev": true,
"license": "ISC"
},
"node_modules/sonic-boom": {
"version": "2.8.0",
"license": "MIT",
"dependencies": {
"atomic-sleep": "^1.0.0"
}
},
"node_modules/source-map-js": {
"version": "1.0.2",
"dev": true,
"license": "BSD-3-Clause",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/split2": {
"version": "4.1.0",
"license": "ISC",
"engines": {
"node": ">= 10.x"
}
},
"node_modules/statuses": {
"version": "1.5.0",
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/stream-shift": {
"version": "1.0.1",
"license": "MIT"
},
"node_modules/string_decoder": {
"version": "1.3.0",
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.2.0"
}
},
"node_modules/string-similarity": {
"version": "4.0.4",
"license": "ISC"
},
"node_modules/string-template": {
"version": "0.2.1"
},
"node_modules/string-width": {
"version": "4.2.3",
"license": "MIT",
"dependencies": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/strip-ansi": {
"version": "6.0.1",
"license": "MIT",
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/strip-json-comments": {
"version": "3.1.1",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/supports-color": {
"version": "7.2.0",
"dev": true,
"license": "MIT",
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/supports-preserve-symlinks-flag": {
"version": "1.0.0",
"license": "MIT",
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/text-table": {
"version": "0.2.0",
"dev": true,
"license": "MIT"
},
"node_modules/thread-stream": {
"version": "0.15.2",
"license": "MIT",
"dependencies": {
"real-require": "^0.1.0"
}
},
"node_modules/thriftrw": {
"version": "3.12.0",
"dependencies": {
"bufrw": "^1.3.0",
"error": "7.0.2",
"long": "^2.4.0"
},
"bin": {
"thrift2json": "thrift2json.js"
},
"engines": {
"node": ">= 0.10.x"
}
},
"node_modules/tiny-lru": {
"version": "8.0.2",
"license": "BSD-3-Clause",
"engines": {
"node": ">=6"
}
},
"node_modules/to-readable-stream": {
"version": "1.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/to-regex-range": {
"version": "5.0.1",
"dev": true,
"license": "MIT",
"dependencies": {
"is-number": "^7.0.0"
},
"engines": {
"node": ">=8.0"
}
},
"node_modules/toidentifier": {
"version": "1.0.1",
"license": "MIT",
"engines": {
"node": ">=0.6"
}
},
"node_modules/touch": {
"version": "3.1.0",
"dev": true,
"license": "ISC",
"dependencies": {
"nopt": "~1.0.10"
},
"bin": {
"nodetouch": "bin/nodetouch.js"
}
},
"node_modules/tr46": {
"version": "0.0.3",
"license": "MIT"
},
"node_modules/type-check": {
"version": "0.4.0",
"dev": true,
"license": "MIT",
"dependencies": {
"prelude-ls": "^1.2.1"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/type-fest": {
"version": "0.20.2",
"dev": true,
"license": "(MIT OR CC0-1.0)",
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/type-is": {
"version": "1.6.18",
"license": "MIT",
"dependencies": {
"media-typer": "0.3.0",
"mime-types": "~2.1.24"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/typedarray-to-buffer": {
"version": "3.1.5",
"dev": true,
"license": "MIT",
"dependencies": {
"is-typedarray": "^1.0.0"
}
},
"node_modules/uhyphen": {
"version": "0.1.0",
"license": "ISC"
},
"node_modules/undefsafe": {
"version": "2.0.5",
"dev": true,
"license": "MIT"
},
"node_modules/unique-string": {
"version": "2.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"crypto-random-string": "^2.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/unpipe": {
"version": "1.0.0",
"license": "MIT",
"engines": {
"node": ">= 0.8"
}
},
"node_modules/update-notifier": {
"version": "5.1.0",
"dev": true,
"license": "BSD-2-Clause",
"dependencies": {
"boxen": "^5.0.0",
"chalk": "^4.1.0",
"configstore": "^5.0.1",
"has-yarn": "^2.1.0",
"import-lazy": "^2.1.0",
"is-ci": "^2.0.0",
"is-installed-globally": "^0.4.0",
"is-npm": "^5.0.0",
"is-yarn-global": "^0.3.0",
"latest-version": "^5.1.0",
"pupa": "^2.1.1",
"semver": "^7.3.4",
"semver-diff": "^3.1.1",
"xdg-basedir": "^4.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/yeoman/update-notifier?sponsor=1"
}
},
"node_modules/update-notifier/node_modules/semver": {
"version": "7.3.5",
"dev": true,
"license": "ISC",
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
"node_modules/uri-js": {
"version": "4.4.1",
"license": "BSD-2-Clause",
"dependencies": {
"punycode": "^2.1.0"
}
},
"node_modules/url-join": {
"version": "4.0.1",
"license": "MIT"
},
"node_modules/url-parse-lax": {
"version": "3.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"prepend-http": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/util-deprecate": {
"version": "1.0.2",
"license": "MIT"
},
"node_modules/utils-merge": {
"version": "1.0.1",
"license": "MIT",
"engines": {
"node": ">= 0.4.0"
}
},
"node_modules/uuid": {
"version": "8.3.2",
"license": "MIT",
"bin": {
"uuid": "dist/bin/uuid"
}
},
"node_modules/v8-compile-cache": {
"version": "2.3.0",
"dev": true,
"license": "MIT"
},
"node_modules/vary": {
"version": "1.1.2",
"license": "MIT",
"engines": {
"node": ">= 0.8"
}
},
"node_modules/vite": {
"version": "2.9.6",
"dev": true,
"license": "MIT",
"dependencies": {
"esbuild": "^0.14.27",
"postcss": "^8.4.12",
"resolve": "^1.22.0",
"rollup": "^2.59.0"
},
"bin": {
"vite": "bin/vite.js"
},
"engines": {
"node": ">=12.2.0"
},
"optionalDependencies": {
"fsevents": "~2.3.2"
},
"peerDependencies": {
"less": "*",
"sass": "*",
"stylus": "*"
},
"peerDependenciesMeta": {
"less": {
"optional": true
},
"sass": {
"optional": true
},
"stylus": {
"optional": true
}
}
},
"node_modules/webidl-conversions": {
"version": "3.0.1",
"license": "BSD-2-Clause"
},
"node_modules/whatwg-url": {
"version": "5.0.0",
"license": "MIT",
"dependencies": {
"tr46": "~0.0.3",
"webidl-conversions": "^3.0.0"
}
},
"node_modules/which": {
"version": "2.0.2",
"dev": true,
"license": "ISC",
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"node-which": "bin/node-which"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/widest-line": {
"version": "3.1.0",
"dev": true,
"license": "MIT",
"dependencies": {
"string-width": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/word-wrap": {
"version": "1.2.3",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/workerpool": {
"version": "6.2.0",
"dev": true,
"license": "Apache-2.0"
},
"node_modules/wrap-ansi": {
"version": "7.0.0",
"license": "MIT",
"dependencies": {
"ansi-styles": "^4.0.0",
"string-width": "^4.1.0",
"strip-ansi": "^6.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/wrap-ansi?sponsor=1"
}
},
"node_modules/wrappy": {
"version": "1.0.2",
"license": "ISC"
},
"node_modules/write-file-atomic": {
"version": "3.0.3",
"dev": true,
"license": "ISC",
"dependencies": {
"imurmurhash": "^0.1.4",
"is-typedarray": "^1.0.0",
"signal-exit": "^3.0.2",
"typedarray-to-buffer": "^3.1.5"
}
},
"node_modules/xdg-basedir": {
"version": "4.0.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
"node_modules/xorshift": {
"version": "1.2.0",
"license": "MIT"
},
"node_modules/xtend": {
"version": "4.0.2",
"license": "MIT",
"engines": {
"node": ">=0.4"
}
},
"node_modules/y18n": {
"version": "5.0.8",
"license": "ISC",
"engines": {
"node": ">=10"
}
},
"node_modules/yallist": {
"version": "4.0.0",
"license": "ISC"
},
"node_modules/yargs": {
"version": "16.2.0",
"license": "MIT",
"dependencies": {
"cliui": "^7.0.2",
"escalade": "^3.1.1",
"get-caller-file": "^2.0.5",
"require-directory": "^2.1.1",
"string-width": "^4.2.0",
"y18n": "^5.0.5",
"yargs-parser": "^20.2.2"
},
"engines": {
"node": ">=10"
}
},
"node_modules/yargs-parser": {
"version": "20.2.4",
"license": "ISC",
"engines": {
"node": ">=10"
}
},
"node_modules/yargs-unparser": {
"version": "2.0.0",
"dev": true,
"license": "MIT",
"dependencies": {
"camelcase": "^6.0.0",
"decamelize": "^4.0.0",
"flat": "^5.0.2",
"is-plain-obj": "^2.1.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/yocto-queue": {
"version": "0.1.0",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"shared": {}
},
"dependencies": {
"@eslint/eslintrc": {
"version": "1.0.5",
"dev": true,
"requires": {
"ajv": "^6.12.4",
"debug": "^4.3.2",
"espree": "^9.2.0",
"globals": "^13.9.0",
"ignore": "^4.0.6",
"import-fresh": "^3.2.1",
"js-yaml": "^4.1.0",
"minimatch": "^3.0.4",
"strip-json-comments": "^3.1.1"
},
"dependencies": {
"debug": {
"version": "4.3.3",
"dev": true,
"requires": {
"ms": "2.1.2"
}
},
"ignore": {
"version": "4.0.6",
"dev": true
},
"ms": {
"version": "2.1.2",
"dev": true
}
}
},
"@fastify/ajv-compiler": {
"version": "1.1.0",
"requires": {
"ajv": "^6.12.6"
}
},
"@fastify/error": {
"version": "2.0.0"
},
"@hapi/b64": {
"version": "5.0.0",
"requires": {
"@hapi/hoek": "9.x.x"
}
},
"@hapi/boom": {
"version": "9.1.4",
"requires": {
"@hapi/hoek": "9.x.x"
}
},
"@hapi/bourne": {
"version": "2.1.0"
},
"@hapi/cryptiles": {
"version": "5.1.0",
"requires": {
"@hapi/boom": "9.x.x"
}
},
"@hapi/hoek": {
"version": "9.3.0"
},
"@hapi/iron": {
"version": "6.0.0",
"requires": {
"@hapi/b64": "5.x.x",
"@hapi/boom": "9.x.x",
"@hapi/bourne": "2.x.x",
"@hapi/cryptiles": "5.x.x",
"@hapi/hoek": "9.x.x"
}
},
"@hapi/podium": {
"version": "4.1.3",
"requires": {
"@hapi/hoek": "9.x.x",
"@hapi/teamwork": "5.x.x",
"@hapi/validate": "1.x.x"
}
},
"@hapi/teamwork": {
"version": "5.1.1"
},
"@hapi/topo": {
"version": "5.1.0",
"requires": {
"@hapi/hoek": "^9.0.0"
}
},
"@hapi/validate": {
"version": "1.1.3",
"requires": {
"@hapi/hoek": "^9.0.0",
"@hapi/topo": "^5.0.0"
}
},
"@humanwhocodes/config-array": {
"version": "0.9.3",
"dev": true,
"requires": {
"@humanwhocodes/object-schema": "^1.2.1",
"debug": "^4.1.1",
"minimatch": "^3.0.4"
},
"dependencies": {
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"debug": {
"version": "4.3.3",
"dev": true,
"requires": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2",
"dev": true
}
}
},
"@humanwhocodes/object-schema": {
"version": "1.2.1",
"dev": true
},
"@matrix-org/olm": {
"version": "https://gitlab.matrix.org/api/v4/projects/27/packages/npm/@matrix-org/olm/-/@matrix-org/olm-3.2.8.tgz",
"integrity": "sha512-yCJzEYY2aG1z+7nxKYZC4DFYwQO/5iG019qgotJhauYJRhEG9gLrKTvXO6lRHS8TjnZzsZFZyO/hQUlI4Dryig=="
},
"@opentelemetry/api": {
"version": "1.1.0"
},
"@opentelemetry/api-metrics": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api": "^1.0.0"
}
},
"@opentelemetry/auto-instrumentations-node": {
"version": "0.31.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/instrumentation-amqplib": "^0.30.0",
"@opentelemetry/instrumentation-aws-lambda": "^0.32.0",
"@opentelemetry/instrumentation-aws-sdk": "^0.8.0",
"@opentelemetry/instrumentation-bunyan": "^0.29.0",
"@opentelemetry/instrumentation-cassandra-driver": "^0.29.0",
"@opentelemetry/instrumentation-connect": "^0.29.0",
"@opentelemetry/instrumentation-dns": "^0.29.0",
"@opentelemetry/instrumentation-express": "^0.30.0",
"@opentelemetry/instrumentation-fastify": "^0.28.0",
"@opentelemetry/instrumentation-generic-pool": "^0.29.0",
"@opentelemetry/instrumentation-graphql": "^0.29.0",
"@opentelemetry/instrumentation-grpc": "^0.29.2",
"@opentelemetry/instrumentation-hapi": "^0.29.0",
"@opentelemetry/instrumentation-http": "^0.29.2",
"@opentelemetry/instrumentation-ioredis": "^0.30.0",
"@opentelemetry/instrumentation-knex": "^0.29.0",
"@opentelemetry/instrumentation-koa": "^0.30.0",
"@opentelemetry/instrumentation-memcached": "^0.29.0",
"@opentelemetry/instrumentation-mongodb": "^0.31.0",
"@opentelemetry/instrumentation-mysql": "^0.30.0",
"@opentelemetry/instrumentation-mysql2": "^0.31.0",
"@opentelemetry/instrumentation-nestjs-core": "^0.30.0",
"@opentelemetry/instrumentation-net": "^0.29.0",
"@opentelemetry/instrumentation-pg": "^0.30.0",
"@opentelemetry/instrumentation-pino": "^0.30.0",
"@opentelemetry/instrumentation-redis": "^0.32.0",
"@opentelemetry/instrumentation-redis-4": "^0.31.0",
"@opentelemetry/instrumentation-restify": "^0.29.0",
"@opentelemetry/instrumentation-winston": "^0.29.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/context-async-hooks": {
"version": "1.4.0",
"requires": {}
},
"@opentelemetry/core": {
"version": "1.4.0",
"requires": {
"@opentelemetry/semantic-conventions": "1.4.0"
},
"dependencies": {
"@opentelemetry/semantic-conventions": {
"version": "1.4.0"
}
}
},
"@opentelemetry/exporter-jaeger": {
"version": "1.3.1",
"requires": {
"@opentelemetry/core": "1.3.1",
"@opentelemetry/sdk-trace-base": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1",
"jaeger-client": "^3.15.0"
},
"dependencies": {
"@opentelemetry/core": {
"version": "1.3.1",
"requires": {
"@opentelemetry/semantic-conventions": "1.3.1"
}
}
}
},
"@opentelemetry/instrumentation": {
"version": "0.30.0",
"requires": {
"@opentelemetry/api-metrics": "0.30.0",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
},
"dependencies": {
"@opentelemetry/api-metrics": {
"version": "0.30.0",
"requires": {
"@opentelemetry/api": "^1.0.0"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-amqplib": {
"version": "0.30.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/amqplib": "^0.5.17"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-aws-lambda": {
"version": "0.32.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/propagator-aws-xray": "^1.1.0",
"@opentelemetry/resources": "^1.0.0",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/aws-lambda": "8.10.81"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-aws-sdk": {
"version": "0.8.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/propagation-utils": "^0.28.0",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-bunyan": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@types/bunyan": "1.8.7"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-cassandra-driver": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-connect": {
"version": "0.29.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/connect": "3.4.35"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-dns": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"semver": "^7.3.2"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-express": {
"version": "0.30.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/express": "4.17.13"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-fastify": {
"version": "0.28.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"fastify": "^3.19.2"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-generic-pool": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/generic-pool": "^3.1.9"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-graphql": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"graphql": "^15.5.1"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-grpc": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"@opentelemetry/instrumentation": "0.29.2",
"@opentelemetry/semantic-conventions": "1.3.1"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-hapi": {
"version": "0.29.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/hapi__hapi": "20.0.9"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/instrumentation-http": {
"version": "0.29.2",
"requires": {
"@opentelemetry/core": "1.3.1",
"@opentelemetry/instrumentation": "0.29.2",
"@opentelemetry/semantic-conventions": "1.3.1",
"semver": "^7.3.5"
},
"dependencies": {
"@opentelemetry/core": {
"version": "1.3.1",
"requires": {
"@opentelemetry/semantic-conventions": "1.3.1"
}
},
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-ioredis": {
"version": "0.30.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/ioredis": "4.26.6"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-knex": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-koa": {
"version": "0.30.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/koa": "2.13.4",
"@types/koa__router": "8.0.7"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-memcached": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/memcached": "^2.2.6"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-mongodb": {
"version": "0.31.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/mongodb": "3.6.20"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-mysql": {
"version": "0.30.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/mysql": "2.15.19"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-mysql2": {
"version": "0.31.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-nestjs-core": {
"version": "0.30.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-net": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-pg": {
"version": "0.30.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/pg": "8.6.1",
"@types/pg-pool": "2.0.3"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-pino": {
"version": "0.30.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"pino": "7.10.0",
"semver": "^7.3.5"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-redis": {
"version": "0.32.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/redis": "2.8.31"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-redis-4": {
"version": "0.31.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-restify": {
"version": "0.29.0",
"requires": {
"@opentelemetry/core": "^1.0.0",
"@opentelemetry/instrumentation": "^0.29.2",
"@opentelemetry/semantic-conventions": "^1.0.0",
"@types/restify": "4.3.8"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/instrumentation-winston": {
"version": "0.29.0",
"requires": {
"@opentelemetry/instrumentation": "^0.29.2"
},
"dependencies": {
"@opentelemetry/instrumentation": {
"version": "0.29.2",
"requires": {
"@opentelemetry/api-metrics": "0.29.2",
"require-in-the-middle": "^5.0.3",
"semver": "^7.3.2",
"shimmer": "^1.2.1"
}
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
"@opentelemetry/propagation-utils": {
"version": "0.28.0",
"requires": {}
},
"@opentelemetry/propagator-aws-xray": {
"version": "1.1.0",
"requires": {
"@opentelemetry/core": "^1.0.0"
}
},
"@opentelemetry/propagator-ot-trace": {
"version": "0.26.0",
"requires": {}
},
"@opentelemetry/resources": {
"version": "1.3.1",
"requires": {
"@opentelemetry/core": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1"
},
"dependencies": {
"@opentelemetry/core": {
"version": "1.3.1",
"requires": {
"@opentelemetry/semantic-conventions": "1.3.1"
}
}
}
},
"@opentelemetry/sdk-trace-base": {
"version": "1.3.1",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"requires": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": "1.3.1",
"@opentelemetry/resources": "1.3.1",
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"dependencies": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/core": {
"version": "1.3.1",
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"requires": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
}
}
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@opentelemetry/semantic-conventions": {
"version": "1.3.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@sideway/address": {
"version": "4.1.4",
"requires": {
"@hapi/hoek": "^9.0.0"
}
},
"@sideway/formula": {
"version": "3.0.0"
},
"@sideway/pinpoint": {
"version": "2.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"@sindresorhus/is": {
"version": "0.14.0",
"dev": true
},
"@szmarczak/http-timer": {
"version": "1.1.2",
"dev": true,
"requires": {
"defer-to-connect": "^1.0.1"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"@types/accepts": {
"version": "1.3.5",
"requires": {
"@types/node": "*"
}
},
"@types/amqplib": {
"version": "0.5.17",
"requires": {
"@types/bluebird": "*",
"@types/node": "*"
}
},
"@types/aws-lambda": {
"version": "8.10.81"
},
"@types/bluebird": {
"version": "3.5.36"
},
"@types/body-parser": {
"version": "1.19.2",
"requires": {
"@types/connect": "*",
"@types/node": "*"
}
},
"@types/bson": {
"version": "4.2.0",
"requires": {
"bson": "*"
}
},
"@types/bunyan": {
"version": "1.8.7",
"requires": {
"@types/node": "*"
}
},
"@types/connect": {
"version": "3.4.35",
"requires": {
"@types/node": "*"
}
},
"@types/content-disposition": {
"version": "0.5.5"
},
"@types/cookies": {
"version": "0.7.7",
"requires": {
"@types/connect": "*",
"@types/express": "*",
"@types/keygrip": "*",
"@types/node": "*"
}
},
"@types/express": {
"version": "4.17.13",
"requires": {
"@types/body-parser": "*",
"@types/express-serve-static-core": "^4.17.18",
"@types/qs": "*",
"@types/serve-static": "*"
}
},
"@types/express-serve-static-core": {
"version": "4.17.29",
"requires": {
"@types/node": "*",
"@types/qs": "*",
"@types/range-parser": "*"
}
},
"@types/generic-pool": {
"version": "3.1.10",
"requires": {
"@types/node": "*"
}
},
"@types/hapi__catbox": {
"version": "10.2.4"
},
"@types/hapi__hapi": {
"version": "20.0.9",
"requires": {
"@hapi/boom": "^9.0.0",
"@hapi/iron": "^6.0.0",
"@hapi/podium": "^4.1.3",
"@types/hapi__catbox": "*",
"@types/hapi__mimos": "*",
"@types/hapi__shot": "*",
"@types/node": "*",
"joi": "^17.3.0"
}
},
"@types/hapi__mimos": {
"version": "4.1.4",
"requires": {
"@types/mime-db": "*"
}
},
"@types/hapi__shot": {
"version": "4.1.2",
"requires": {
"@types/node": "*"
}
},
"@types/http-assert": {
"version": "1.5.3"
},
"@types/http-errors": {
"version": "1.8.2"
},
"@types/ioredis": {
"version": "4.26.6",
"requires": {
"@types/node": "*"
}
},
"@types/keygrip": {
"version": "1.0.2"
},
"@types/koa": {
"version": "2.13.4",
"requires": {
"@types/accepts": "*",
"@types/content-disposition": "*",
"@types/cookies": "*",
"@types/http-assert": "*",
"@types/http-errors": "*",
"@types/keygrip": "*",
"@types/koa-compose": "*",
"@types/node": "*"
}
},
"@types/koa__router": {
"version": "8.0.7",
"requires": {
"@types/koa": "*"
}
},
"@types/koa-compose": {
"version": "3.2.5",
"requires": {
"@types/koa": "*"
}
},
"@types/memcached": {
"version": "2.2.7",
"requires": {
"@types/node": "*"
}
},
"@types/mime": {
"version": "1.3.2"
},
"@types/mime-db": {
"version": "1.43.1"
},
"@types/mongodb": {
"version": "3.6.20",
"requires": {
"@types/bson": "*",
"@types/node": "*"
}
},
"@types/mysql": {
"version": "2.15.19",
"requires": {
"@types/node": "*"
}
},
"@types/node": {
"version": "18.0.0"
},
"@types/pg": {
"version": "8.6.1",
"requires": {
"@types/node": "*",
"pg-protocol": "*",
"pg-types": "^2.2.0"
}
},
"@types/pg-pool": {
"version": "2.0.3",
"requires": {
"@types/pg": "*"
}
},
"@types/qs": {
"version": "6.9.7"
},
"@types/range-parser": {
"version": "1.2.4"
},
"@types/redis": {
"version": "2.8.31",
"requires": {
"@types/node": "*"
}
},
"@types/restify": {
"version": "4.3.8",
"requires": {
"@types/bunyan": "*",
"@types/node": "*"
}
},
"@types/serve-static": {
"version": "1.13.10",
"requires": {
"@types/mime": "^1",
"@types/node": "*"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"@ungap/promise-all-settled": {
"version": "1.1.2",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"abbrev": {
"version": "1.1.1",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"abstract-logging": {
"version": "2.0.1"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"accepts": {
"version": "1.3.8",
"requires": {
"mime-types": "~2.1.34",
"negotiator": "0.6.3"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"acorn": {
"version": "8.7.0",
"dev": true
},
"acorn-jsx": {
"version": "5.3.2",
"dev": true,
"requires": {}
},
"ajv": {
"version": "6.12.6",
"requires": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"another-json": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.2.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"ansi-align": {
"version": "3.0.1",
"dev": true,
"requires": {
"string-width": "^4.1.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ansi-color": {
"version": "0.2.1"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"ansi-colors": {
"version": "4.1.1",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"ansi-regex": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "5.0.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"ansi-styles": {
"version": "4.3.0",
"requires": {
"color-convert": "^2.0.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"anymatch": {
"version": "3.1.2",
"dev": true,
"requires": {
"normalize-path": "^3.0.0",
"picomatch": "^2.0.4"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"archy": {
"version": "1.0.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"argparse": {
"version": "2.0.1",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"array-flatten": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"async": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.5.2"
},
"atomic-sleep": {
"version": "1.0.0"
},
"avvio": {
"version": "7.2.5",
"requires": {
"archy": "^1.0.0",
"debug": "^4.0.0",
"fastq": "^1.6.1",
"queue-microtask": "^1.1.2"
},
"dependencies": {
"debug": {
"version": "4.3.4",
"requires": {
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2"
}
}
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"balanced-match": {
"version": "1.0.2",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"base64-arraybuffer": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.2.0"
},
"base64-js": {
"version": "1.5.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"binary-extensions": {
"version": "2.2.0",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"body-parser": {
"version": "1.19.1",
"requires": {
"bytes": "3.1.1",
"content-type": "~1.0.4",
"debug": "2.6.9",
"depd": "~1.1.2",
"http-errors": "1.8.1",
"iconv-lite": "0.4.24",
"on-finished": "~2.3.0",
"qs": "6.9.6",
"raw-body": "2.4.2",
"type-is": "~1.6.18"
}
},
"boolbase": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"boxen": {
"version": "5.1.2",
"dev": true,
"requires": {
"ansi-align": "^3.0.0",
"camelcase": "^6.2.0",
"chalk": "^4.1.0",
"cli-boxes": "^2.2.1",
"string-width": "^4.2.2",
"type-fest": "^0.20.2",
"widest-line": "^3.1.0",
"wrap-ansi": "^7.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"brace-expansion": {
"version": "1.1.11",
"dev": true,
"requires": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"braces": {
"version": "3.0.2",
"dev": true,
"requires": {
"fill-range": "^7.0.1"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"browser-stdout": {
"version": "1.3.1",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"bson": {
"version": "4.6.4",
"requires": {
"buffer": "^5.6.0"
}
},
"buffer": {
"version": "5.7.1",
"requires": {
"base64-js": "^1.3.1",
"ieee754": "^1.1.13"
}
},
"bufrw": {
"version": "1.3.0",
"requires": {
"ansi-color": "^0.2.1",
"error": "^7.0.0",
"hexer": "^1.5.0",
"xtend": "^4.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"bytes": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.1.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"cacheable-request": {
"version": "6.1.0",
"dev": true,
"requires": {
"clone-response": "^1.0.2",
"get-stream": "^5.1.0",
"http-cache-semantics": "^4.0.0",
"keyv": "^3.0.0",
"lowercase-keys": "^2.0.0",
"normalize-url": "^4.1.0",
"responselike": "^1.0.2"
},
"dependencies": {
"get-stream": {
"version": "5.2.0",
"dev": true,
"requires": {
"pump": "^3.0.0"
}
},
"lowercase-keys": {
"version": "2.0.0",
"dev": true
}
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"callsites": {
"version": "3.1.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"camelcase": {
"version": "6.3.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"chalk": {
"version": "4.1.2",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"requires": {
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"chokidar": {
"version": "3.5.3",
"dev": true,
"requires": {
"anymatch": "~3.1.2",
"braces": "~3.0.2",
"fsevents": "~2.3.2",
"glob-parent": "~5.1.2",
"is-binary-path": "~2.1.0",
"is-glob": "~4.0.1",
"normalize-path": "~3.0.0",
"readdirp": "~3.6.0"
},
"dependencies": {
"glob-parent": {
"version": "5.1.2",
"dev": true,
"requires": {
"is-glob": "^4.0.1"
}
}
}
},
"ci-info": {
"version": "2.0.0",
"dev": true
},
"cli-boxes": {
"version": "2.2.1",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"cliui": {
"version": "7.0.4",
"requires": {
"string-width": "^4.2.0",
"strip-ansi": "^6.0.0",
"wrap-ansi": "^7.0.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"clone-response": {
"version": "1.0.2",
"dev": true,
"requires": {
"mimic-response": "^1.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"color-convert": {
"version": "2.0.1",
"requires": {
"color-name": "~1.1.4"
}
},
"color-name": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.4"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"concat-map": {
"version": "0.0.1",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"configstore": {
"version": "5.0.1",
"dev": true,
"requires": {
"dot-prop": "^5.2.0",
"graceful-fs": "^4.1.2",
"make-dir": "^3.0.0",
"unique-string": "^2.0.0",
"write-file-atomic": "^3.0.0",
"xdg-basedir": "^4.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"content-disposition": {
"version": "0.5.4",
"requires": {
"safe-buffer": "5.2.1"
}
},
"content-type": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.4"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"cookie": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.4.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"cookie-signature": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.6"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
"core-js": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.23.1"
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"cross-spawn": {
"version": "7.0.3",
"dev": true,
"requires": {
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"crypto-random-string": {
"version": "2.0.0",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"css-select": {
"version": "4.2.1",
"requires": {
"boolbase": "^1.0.0",
"css-what": "^5.1.0",
"domhandler": "^4.3.0",
"domutils": "^2.8.0",
"nth-check": "^2.0.1"
}
},
"css-what": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "5.1.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"cssom": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.5.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"debug": {
"version": "2.6.9",
"requires": {
"ms": "2.0.0"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"decamelize": {
"version": "4.0.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"decompress-response": {
"version": "3.3.0",
"dev": true,
"requires": {
"mimic-response": "^1.0.0"
}
},
"deep-extend": {
"version": "0.6.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"deep-is": {
"version": "0.1.4",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"deepmerge": {
"version": "4.2.2"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"defer-to-connect": {
"version": "1.1.3",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"depd": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.2"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"destroy": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.4"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"diff": {
"version": "5.0.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"doctrine": {
"version": "3.0.0",
"dev": true,
"requires": {
"esutils": "^2.0.2"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"dom-serializer": {
"version": "1.3.2",
"requires": {
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"domelementtype": "^2.0.1",
"domhandler": "^4.2.0",
"entities": "^2.0.0"
}
},
"domelementtype": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.2.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"domhandler": {
"version": "4.3.0",
"requires": {
"domelementtype": "^2.2.0"
}
},
"dompurify": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.3.9"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"domutils": {
"version": "2.8.0",
"requires": {
"dom-serializer": "^1.0.1",
"domelementtype": "^2.2.0",
"domhandler": "^4.2.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dot-prop": {
"version": "5.3.0",
"dev": true,
"requires": {
"is-obj": "^2.0.0"
}
},
"duplexer3": {
"version": "0.1.4",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"duplexify": {
"version": "4.1.2",
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"requires": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"end-of-stream": "^1.4.1",
"inherits": "^2.0.3",
"readable-stream": "^3.1.1",
"stream-shift": "^1.0.0"
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ee-first": {
"version": "1.1.1"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"emoji-regex": {
"version": "8.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"encodeurl": {
"version": "1.0.2"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"end-of-stream": {
"version": "1.4.4",
"requires": {
"once": "^1.4.0"
}
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"entities": {
"version": "2.2.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"error": {
"version": "7.0.2",
"requires": {
"string-template": "~0.2.1",
"xtend": "~4.0.0"
}
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"esbuild": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"version": "0.14.31",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dev": true,
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"requires": {
"esbuild-android-64": "0.14.31",
"esbuild-android-arm64": "0.14.31",
"esbuild-darwin-64": "0.14.31",
"esbuild-darwin-arm64": "0.14.31",
"esbuild-freebsd-64": "0.14.31",
"esbuild-freebsd-arm64": "0.14.31",
"esbuild-linux-32": "0.14.31",
"esbuild-linux-64": "0.14.31",
"esbuild-linux-arm": "0.14.31",
"esbuild-linux-arm64": "0.14.31",
"esbuild-linux-mips64le": "0.14.31",
"esbuild-linux-ppc64le": "0.14.31",
"esbuild-linux-riscv64": "0.14.31",
"esbuild-linux-s390x": "0.14.31",
"esbuild-netbsd-64": "0.14.31",
"esbuild-openbsd-64": "0.14.31",
"esbuild-sunos-64": "0.14.31",
"esbuild-windows-32": "0.14.31",
"esbuild-windows-64": "0.14.31",
"esbuild-windows-arm64": "0.14.31"
}
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
"esbuild-windows-64": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"version": "0.14.31",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dev": true,
"optional": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"escalade": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.1.1"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"escape-goat": {
"version": "2.1.1",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"escape-html": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.3"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"escape-string-regexp": {
"version": "4.0.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"eslint": {
"version": "8.8.0",
"dev": true,
"requires": {
"@eslint/eslintrc": "^1.0.5",
"@humanwhocodes/config-array": "^0.9.2",
"ajv": "^6.10.0",
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
"debug": "^4.3.2",
"doctrine": "^3.0.0",
"escape-string-regexp": "^4.0.0",
"eslint-scope": "^7.1.0",
"eslint-utils": "^3.0.0",
"eslint-visitor-keys": "^3.2.0",
"espree": "^9.3.0",
"esquery": "^1.4.0",
"esutils": "^2.0.2",
"fast-deep-equal": "^3.1.3",
"file-entry-cache": "^6.0.1",
"functional-red-black-tree": "^1.0.1",
"glob-parent": "^6.0.1",
"globals": "^13.6.0",
"ignore": "^5.2.0",
"import-fresh": "^3.0.0",
"imurmurhash": "^0.1.4",
"is-glob": "^4.0.0",
"js-yaml": "^4.1.0",
"json-stable-stringify-without-jsonify": "^1.0.1",
"levn": "^0.4.1",
"lodash.merge": "^4.6.2",
"minimatch": "^3.0.4",
"natural-compare": "^1.4.0",
"optionator": "^0.9.1",
"regexpp": "^3.2.0",
"strip-ansi": "^6.0.1",
"strip-json-comments": "^3.1.0",
"text-table": "^0.2.0",
"v8-compile-cache": "^2.0.3"
},
"dependencies": {
"debug": {
"version": "4.3.3",
"dev": true,
"requires": {
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2",
"dev": true
}
}
},
"eslint-config-prettier": {
"version": "8.3.0",
"dev": true,
"requires": {}
},
"eslint-plugin-es": {
"version": "3.0.1",
"dev": true,
"requires": {
"eslint-utils": "^2.0.0",
"regexpp": "^3.0.0"
},
"dependencies": {
"eslint-utils": {
"version": "2.1.0",
"dev": true,
"requires": {
"eslint-visitor-keys": "^1.1.0"
}
},
"eslint-visitor-keys": {
"version": "1.3.0",
"dev": true
}
}
},
"eslint-plugin-node": {
"version": "11.1.0",
"dev": true,
"requires": {
"eslint-plugin-es": "^3.0.0",
"eslint-utils": "^2.0.0",
"ignore": "^5.1.1",
"minimatch": "^3.0.4",
"resolve": "^1.10.1",
"semver": "^6.1.0"
},
"dependencies": {
"eslint-utils": {
"version": "2.1.0",
"dev": true,
"requires": {
"eslint-visitor-keys": "^1.1.0"
}
},
"eslint-visitor-keys": {
"version": "1.3.0",
"dev": true
}
}
},
"eslint-plugin-prettier": {
"version": "4.0.0",
"dev": true,
"requires": {
"prettier-linter-helpers": "^1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"eslint-scope": {
"version": "7.1.0",
"dev": true,
"requires": {
"esrecurse": "^4.3.0",
"estraverse": "^5.2.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"eslint-utils": {
"version": "3.0.0",
"dev": true,
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"requires": {
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"eslint-visitor-keys": "^2.0.0"
},
"dependencies": {
"eslint-visitor-keys": {
"version": "2.1.0",
"dev": true
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"eslint-visitor-keys": {
"version": "3.2.0",
"dev": true
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"espree": {
"version": "9.3.0",
"dev": true,
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"requires": {
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"acorn": "^8.7.0",
"acorn-jsx": "^5.3.1",
"eslint-visitor-keys": "^3.1.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"esquery": {
"version": "1.4.0",
"dev": true,
"requires": {
"estraverse": "^5.1.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"esrecurse": {
"version": "4.3.0",
"dev": true,
"requires": {
"estraverse": "^5.2.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"estraverse": {
"version": "5.3.0",
"dev": true
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"esutils": {
"version": "2.0.3",
"dev": true
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"etag": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.8.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"express": {
"version": "4.17.2",
"requires": {
"accepts": "~1.3.7",
"array-flatten": "1.1.1",
"body-parser": "1.19.1",
"content-disposition": "0.5.4",
"content-type": "~1.0.4",
"cookie": "0.4.1",
"cookie-signature": "1.0.6",
"debug": "2.6.9",
"depd": "~1.1.2",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"finalhandler": "~1.1.2",
"fresh": "0.5.2",
"merge-descriptors": "1.0.1",
"methods": "~1.1.2",
"on-finished": "~2.3.0",
"parseurl": "~1.3.3",
"path-to-regexp": "0.1.7",
"proxy-addr": "~2.0.7",
"qs": "6.9.6",
"range-parser": "~1.2.1",
"safe-buffer": "5.2.1",
"send": "0.17.2",
"serve-static": "1.14.2",
"setprototypeof": "1.2.0",
"statuses": "~1.5.0",
"type-is": "~1.6.18",
"utils-merge": "1.0.1",
"vary": "~1.1.2"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"fast-decode-uri-component": {
"version": "1.0.1"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"fast-deep-equal": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.1.3"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"fast-diff": {
"version": "1.2.0",
"dev": true
},
"fast-json-stable-stringify": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.1.0"
},
"fast-json-stringify": {
"version": "2.7.13",
"requires": {
"ajv": "^6.11.0",
"deepmerge": "^4.2.2",
"rfdc": "^1.2.0",
"string-similarity": "^4.0.1"
}
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"fast-levenshtein": {
"version": "2.0.6",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"fast-redact": {
"version": "3.1.1"
},
"fast-safe-stringify": {
"version": "2.1.1"
},
"fastify": {
"version": "3.29.0",
"requires": {
"@fastify/ajv-compiler": "^1.0.0",
"@fastify/error": "^2.0.0",
"abstract-logging": "^2.0.0",
"avvio": "^7.1.2",
"fast-json-stringify": "^2.5.2",
"find-my-way": "^4.5.0",
"flatstr": "^1.0.12",
"light-my-request": "^4.2.0",
"pino": "^6.13.0",
"process-warning": "^1.0.0",
"proxy-addr": "^2.0.7",
"rfdc": "^1.1.4",
"secure-json-parse": "^2.0.0",
"semver": "^7.3.2",
"tiny-lru": "^8.0.1"
},
"dependencies": {
"pino": {
"version": "6.14.0",
"requires": {
"fast-redact": "^3.0.0",
"fast-safe-stringify": "^2.0.8",
"flatstr": "^1.0.12",
"pino-std-serializers": "^3.1.0",
"process-warning": "^1.0.0",
"quick-format-unescaped": "^4.0.3",
"sonic-boom": "^1.0.2"
}
},
"pino-std-serializers": {
"version": "3.2.0"
},
"semver": {
"version": "7.3.7",
"requires": {
"lru-cache": "^6.0.0"
}
},
"sonic-boom": {
"version": "1.4.1",
"requires": {
"atomic-sleep": "^1.0.0",
"flatstr": "^1.0.12"
}
}
}
},
"fastq": {
"version": "1.13.0",
"requires": {
"reusify": "^1.0.4"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"file-entry-cache": {
"version": "6.0.1",
"dev": true,
"requires": {
"flat-cache": "^3.0.4"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"fill-range": {
"version": "7.0.1",
"dev": true,
"requires": {
"to-regex-range": "^5.0.1"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"finalhandler": {
"version": "1.1.2",
"requires": {
"debug": "2.6.9",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"on-finished": "~2.3.0",
"parseurl": "~1.3.3",
"statuses": "~1.5.0",
"unpipe": "~1.0.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"find-my-way": {
"version": "4.5.1",
"requires": {
"fast-decode-uri-component": "^1.0.1",
"fast-deep-equal": "^3.1.3",
"safe-regex2": "^2.0.0",
"semver-store": "^0.3.0"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"find-up": {
"version": "5.0.0",
"dev": true,
"requires": {
"locate-path": "^6.0.0",
"path-exists": "^4.0.0"
}
},
"flat": {
"version": "5.0.2",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"flat-cache": {
"version": "3.0.4",
"dev": true,
"requires": {
"flatted": "^3.1.0",
"rimraf": "^3.0.2"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"flatstr": {
"version": "1.0.12"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"flatted": {
"version": "3.2.5",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"forwarded": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.2.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"fresh": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.5.2"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"fs.realpath": {
"version": "1.0.0",
"dev": true
},
"function-bind": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"functional-red-black-tree": {
"version": "1.0.1",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"get-caller-file": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.0.5"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"get-stream": {
"version": "4.1.0",
"dev": true,
"requires": {
"pump": "^3.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"glob": {
"version": "7.2.0",
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
"glob-parent": {
"version": "6.0.2",
"dev": true,
"requires": {
"is-glob": "^4.0.3"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"global-dirs": {
"version": "3.0.0",
"dev": true,
"requires": {
"ini": "2.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"globals": {
"version": "13.12.1",
"dev": true,
"requires": {
"type-fest": "^0.20.2"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"got": {
"version": "9.6.0",
"dev": true,
"requires": {
"@sindresorhus/is": "^0.14.0",
"@szmarczak/http-timer": "^1.1.2",
"cacheable-request": "^6.0.0",
"decompress-response": "^3.3.0",
"duplexer3": "^0.1.4",
"get-stream": "^4.1.0",
"lowercase-keys": "^1.0.1",
"mimic-response": "^1.0.1",
"p-cancelable": "^1.0.0",
"to-readable-stream": "^1.0.0",
"url-parse-lax": "^3.0.0"
}
},
"graceful-fs": {
"version": "4.2.9",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"graphql": {
"version": "15.8.0"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"growl": {
"version": "1.10.5",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"has": {
"version": "1.0.3",
"requires": {
"function-bind": "^1.1.1"
}
},
"has-flag": {
"version": "4.0.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"has-yarn": {
"version": "2.1.0",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"he": {
"version": "1.2.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"hexer": {
"version": "1.5.0",
"requires": {
"ansi-color": "^0.2.1",
"minimist": "^1.1.0",
"process": "^0.10.0",
"xtend": "^4.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"html-escaper": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.0.3"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"htmlparser2": {
"version": "7.2.0",
"requires": {
"domelementtype": "^2.0.1",
"domhandler": "^4.2.2",
"domutils": "^2.8.0",
"entities": "^3.0.1"
},
"dependencies": {
"entities": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.0.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"http-cache-semantics": {
"version": "4.1.0",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"http-errors": {
"version": "1.8.1",
"requires": {
"depd": "~1.1.2",
"inherits": "2.0.4",
"setprototypeof": "1.2.0",
"statuses": ">= 1.5.0 < 2",
"toidentifier": "1.0.1"
}
},
"hydrogen-view-sdk": {
Fix missing `room.observePowerLevels()` throwing error after render (#57) Fix missing `room.observePowerLevels()` throwing error after render. ``` Uncaught (in promise) TypeError: this._room.observePowerLevels is not a function at RoomViewModel2._recreateComposerOnPowerLevelChange (matrix-public-archive.js:23498:53) at new RoomViewModel2 (matrix-public-archive.js:23469:14) at mountHydrogen (matrix-public-archive.js:27131:25) at matrix-public-archive.js:27174:1 ``` Doesn't affect main-line rendering but the error is annoying to see. More Hydrogen boilerplate 😞
2022-08-30 22:40:07 -06:00
"version": "npm:@mlm/hydrogen-view-sdk@0.15.0-scratch",
"resolved": "https://registry.npmjs.org/@mlm/hydrogen-view-sdk/-/hydrogen-view-sdk-0.15.0-scratch.tgz",
"integrity": "sha512-QRsJjk56EdMWWgSEewLOG0FgRPqP8Yyc15fyU+60GzBrSL/fh6jfkgGejLHuJbPYFcKnkPpCTDEbEDLfP2kjaQ==",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"requires": {
Use stable test selectors from Hydrogen (`data-testid`) Follow-up to https://github.com/matrix-org/matrix-public-archive/pull/29#discussion_r909492946 --- Updated Hydrogen to add the consistent `data-testid` attribute selectors, https://github.com/vector-im/hydrogen-web/pull/773 ``` npm install hydrogen-view-sdk@npm:@mlm/hydrogen-view-sdk@0.0.13-scratch ```
2022-07-05 05:23:47 -06:00
"@matrix-org/olm": "https://gitlab.matrix.org/api/v4/projects/27/packages/npm/@matrix-org/olm/-/@matrix-org/olm-3.2.8.tgz",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"another-json": "^0.2.0",
"base64-arraybuffer": "^0.2.0",
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
"dompurify": "^2.3.0",
"off-color": "^2.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
},
"iconv-lite": {
"version": "0.4.24",
"requires": {
"safer-buffer": ">= 2.1.2 < 3"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ieee754": {
"version": "1.2.1"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"ignore": {
"version": "5.2.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"ignore-by-default": {
"version": "1.0.1",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"import-fresh": {
"version": "3.3.0",
"dev": true,
"requires": {
"parent-module": "^1.0.0",
"resolve-from": "^4.0.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"import-lazy": {
"version": "2.1.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"imurmurhash": {
"version": "0.1.4",
"dev": true
},
"inflight": {
"version": "1.0.6",
"dev": true,
"requires": {
"once": "^1.3.0",
"wrappy": "1"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"inherits": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.0.4"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"ini": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"ipaddr.js": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.9.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"is-binary-path": {
"version": "2.1.0",
"dev": true,
"requires": {
"binary-extensions": "^2.0.0"
}
},
"is-ci": {
"version": "2.0.0",
"dev": true,
"requires": {
"ci-info": "^2.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"is-core-module": {
"version": "2.8.1",
"requires": {
"has": "^1.0.3"
}
},
"is-extglob": {
"version": "2.1.1",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"is-fullwidth-code-point": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.0.0"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"is-glob": {
"version": "4.0.3",
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"is-installed-globally": {
"version": "0.4.0",
"dev": true,
"requires": {
"global-dirs": "^3.0.0",
"is-path-inside": "^3.0.2"
}
},
"is-npm": {
"version": "5.0.0",
"dev": true
},
"is-number": {
"version": "7.0.0",
"dev": true
},
"is-obj": {
"version": "2.0.0",
"dev": true
},
"is-path-inside": {
"version": "3.0.3",
"dev": true
},
"is-plain-obj": {
"version": "2.1.0",
"dev": true
},
"is-typedarray": {
"version": "1.0.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"is-unicode-supported": {
"version": "0.1.0",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"dev": true
},
"is-yarn-global": {
"version": "0.3.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"isexe": {
"version": "2.0.0",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"jaeger-client": {
"version": "3.19.0",
"requires": {
"node-int64": "^0.4.0",
"opentracing": "^0.14.4",
"thriftrw": "^3.5.0",
"uuid": "^8.3.2",
"xorshift": "^1.1.1"
}
},
"joi": {
"version": "17.6.0",
"requires": {
"@hapi/hoek": "^9.0.0",
"@hapi/topo": "^5.0.0",
"@sideway/address": "^4.1.3",
"@sideway/formula": "^3.0.0",
"@sideway/pinpoint": "^2.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"js-yaml": {
"version": "4.1.0",
"dev": true,
"requires": {
"argparse": "^2.0.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"json-buffer": {
"version": "3.0.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"json-schema-traverse": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.4.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"json-stable-stringify-without-jsonify": {
"version": "1.0.1",
"dev": true
},
Use JSON5 for configuration files with comments (#52) Use JSON5 for configuration files with comments. Now we can leave the available config in `config.default.json` without having to add weird instructions to remove the `xxx`, etc - https://www.npmjs.com/package/json5 - https://www.npmjs.com/package/nconf - https://github.com/indexzero/nconf/issues/113#issuecomment-69999413
2022-08-29 19:33:02 -06:00
"json5": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.1.tgz",
"integrity": "sha512-1hqLFMSrGHRHxav9q9gNjJ5EXznIxGVO09xQRrwplcS8qs28pZ8s8hupZAmqDwZUmVZ2Qb2jnyPOWcDH8m8dlA=="
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"keyv": {
"version": "3.1.0",
"dev": true,
"requires": {
"json-buffer": "3.0.0"
}
},
"latest-version": {
"version": "5.1.0",
"dev": true,
"requires": {
"package-json": "^6.3.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"levn": {
"version": "0.4.1",
"dev": true,
"requires": {
"prelude-ls": "^1.2.1",
"type-check": "~0.4.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"light-my-request": {
"version": "4.10.1",
"requires": {
"ajv": "^8.1.0",
"cookie": "^0.5.0",
"process-warning": "^1.0.0",
"set-cookie-parser": "^2.4.1"
},
"dependencies": {
"ajv": {
"version": "8.11.0",
"requires": {
"fast-deep-equal": "^3.1.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2",
"uri-js": "^4.2.2"
}
},
"cookie": {
"version": "0.5.0"
},
"json-schema-traverse": {
"version": "1.0.0"
}
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"linkedom": {
WIP: Add calendar to right panel
2022-02-14 20:11:55 -07:00
"version": "0.14.1",
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"requires": {
"css-select": "^4.2.1",
"cssom": "^0.5.0",
"html-escaper": "^3.0.3",
"htmlparser2": "^7.2.0",
"uhyphen": "^0.1.0"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"locate-path": {
"version": "6.0.0",
"dev": true,
"requires": {
"p-locate": "^5.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"lodash.merge": {
"version": "4.6.2",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"log-symbols": {
"version": "4.1.0",
"dev": true,
"requires": {
"chalk": "^4.1.0",
"is-unicode-supported": "^0.1.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"long": {
"version": "2.4.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"lowercase-keys": {
"version": "1.0.1",
"dev": true
},
"lru-cache": {
"version": "6.0.0",
"requires": {
"yallist": "^4.0.0"
}
},
"make-dir": {
"version": "3.1.0",
"dev": true,
"requires": {
"semver": "^6.0.0"
}
},
Add custom RightPanel support
2022-02-10 01:21:49 -07:00
"matrix-public-archive-shared": {
"version": "file:shared"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"media-typer": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.3.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"merge-descriptors": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"merge-options": {
"version": "3.0.4",
"dev": true,
"requires": {
"is-plain-obj": "^2.1.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"methods": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.2"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"mime": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.6.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"mime-db": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.51.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"mime-types": {
"version": "2.1.34",
"requires": {
"mime-db": "1.51.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"mimic-response": {
"version": "1.0.1",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"minimatch": {
"version": "3.0.5",
"dev": true,
"requires": {
"brace-expansion": "^1.1.7"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"minimist": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.2.6"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"mocha": {
"version": "9.2.1",
"dev": true,
"requires": {
"@ungap/promise-all-settled": "1.1.2",
"ansi-colors": "4.1.1",
"browser-stdout": "1.3.1",
"chokidar": "3.5.3",
"debug": "4.3.3",
"diff": "5.0.0",
"escape-string-regexp": "4.0.0",
"find-up": "5.0.0",
"glob": "7.2.0",
"growl": "1.10.5",
"he": "1.2.0",
"js-yaml": "4.1.0",
"log-symbols": "4.1.0",
"minimatch": "3.0.4",
"ms": "2.1.3",
"nanoid": "3.2.0",
"serialize-javascript": "6.0.0",
"strip-json-comments": "3.1.1",
"supports-color": "8.1.1",
"which": "2.0.2",
"workerpool": "6.2.0",
"yargs": "16.2.0",
"yargs-parser": "20.2.4",
"yargs-unparser": "2.0.0"
},
"dependencies": {
"debug": {
"version": "4.3.3",
"dev": true,
"requires": {
"ms": "2.1.2"
},
"dependencies": {
"ms": {
"version": "2.1.2",
"dev": true
}
}
},
"minimatch": {
"version": "3.0.4",
"dev": true,
"requires": {
"brace-expansion": "^1.1.7"
}
},
"ms": {
"version": "2.1.3",
"dev": true
},
"nanoid": {
"version": "3.2.0",
"dev": true
},
"supports-color": {
"version": "8.1.1",
"dev": true,
"requires": {
"has-flag": "^4.0.0"
}
}
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"module-details-from-path": {
"version": "1.0.3"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"ms": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"nanoid": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"version": "3.3.4",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"natural-compare": {
"version": "1.4.0",
"dev": true
},
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"nconf": {
"version": "0.11.3",
"requires": {
"async": "^1.4.0",
"ini": "^2.0.0",
"secure-keys": "^1.0.0",
"yargs": "^16.1.1"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"negotiator": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.6.3"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"node-fetch": {
"version": "2.6.7",
"requires": {
"whatwg-url": "^5.0.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"node-int64": {
"version": "0.4.0"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"nodemon": {
"version": "2.0.15",
"dev": true,
"requires": {
"chokidar": "^3.5.2",
"debug": "^3.2.7",
"ignore-by-default": "^1.0.1",
"minimatch": "^3.0.4",
"pstree.remy": "^1.1.8",
"semver": "^5.7.1",
"supports-color": "^5.5.0",
"touch": "^3.1.0",
"undefsafe": "^2.0.5",
"update-notifier": "^5.1.0"
},
"dependencies": {
"debug": {
"version": "3.2.7",
"dev": true,
"requires": {
"ms": "^2.1.1"
}
},
"has-flag": {
"version": "3.0.0",
"dev": true
},
"ms": {
"version": "2.1.3",
"dev": true
},
"semver": {
"version": "5.7.1",
"dev": true
},
"supports-color": {
"version": "5.5.0",
"dev": true,
"requires": {
"has-flag": "^3.0.0"
}
}
}
},
"nopt": {
"version": "1.0.10",
"dev": true,
"requires": {
"abbrev": "1"
}
},
"normalize-path": {
"version": "3.0.0",
"dev": true
},
"normalize-url": {
"version": "4.5.1",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"nth-check": {
"version": "2.0.1",
"requires": {
"boolbase": "^1.0.0"
}
},
Add testing to CI (#20) 1. Build test homeserver Docker images which can federate with each other 2. Run end-to-end (e2e) tests #### Dev notes Sharing variables across jobs when the `services` field can't access the `env` context, https://github.community/t/how-to-use-env-with-container-image/17252/24 ```yaml env: FOO: bar jobs: set_env: outputs: var: ${{ steps.save_var.outputs.var }} steps: - id: save_var run: echo "::set-output name=var::${{ env.FOO }}" actual_job: needs: set_env container: image: ...whatever_you_need_here...${{ needs.set_env.outputs.var }} ```
2022-06-14 23:59:41 -06:00
"off-color": {
"version": "2.0.0",
"requires": {
"core-js": "^3.6.5"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"on-exit-leak-free": {
"version": "0.2.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"on-finished": {
"version": "2.3.0",
"requires": {
"ee-first": "1.1.1"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"once": {
"version": "1.4.0",
"requires": {
"wrappy": "1"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"opentracing": {
"version": "0.14.7"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"optionator": {
"version": "0.9.1",
"dev": true,
"requires": {
"deep-is": "^0.1.3",
"fast-levenshtein": "^2.0.6",
"levn": "^0.4.1",
"prelude-ls": "^1.2.1",
"type-check": "^0.4.0",
"word-wrap": "^1.2.3"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"p-cancelable": {
"version": "1.1.0",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"p-limit": {
"version": "3.1.0",
"dev": true,
"requires": {
"yocto-queue": "^0.1.0"
}
},
"p-locate": {
"version": "5.0.0",
"dev": true,
"requires": {
"p-limit": "^3.0.2"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"package-json": {
"version": "6.5.0",
"dev": true,
"requires": {
"got": "^9.6.0",
"registry-auth-token": "^4.0.0",
"registry-url": "^5.0.0",
"semver": "^6.2.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"parent-module": {
"version": "1.0.1",
"dev": true,
"requires": {
"callsites": "^3.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"parseurl": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.3.3"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"path-exists": {
"version": "4.0.0",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"path-is-absolute": {
"version": "1.0.1",
"dev": true
},
"path-key": {
"version": "3.1.1",
"dev": true
},
"path-parse": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.7"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"path-to-regexp": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.1.7"
},
"pg-int8": {
"version": "1.0.1"
},
"pg-protocol": {
"version": "1.5.0"
},
"pg-types": {
"version": "2.2.0",
"requires": {
"pg-int8": "1.0.1",
"postgres-array": "~2.0.0",
"postgres-bytea": "~1.0.0",
"postgres-date": "~1.0.4",
"postgres-interval": "^1.1.0"
}
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"picocolors": {
"version": "1.0.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"picomatch": {
"version": "2.3.1",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"pino": {
"version": "7.10.0",
"requires": {
"atomic-sleep": "^1.0.0",
"fast-redact": "^3.0.0",
"on-exit-leak-free": "^0.2.0",
"pino-abstract-transport": "v0.5.0",
"pino-std-serializers": "^4.0.0",
"process-warning": "^1.0.0",
"quick-format-unescaped": "^4.0.3",
"real-require": "^0.1.0",
"safe-stable-stringify": "^2.1.0",
"sonic-boom": "^2.2.1",
"thread-stream": "^0.15.1"
}
},
"pino-abstract-transport": {
"version": "0.5.0",
"requires": {
"duplexify": "^4.1.2",
"split2": "^4.0.0"
}
},
"pino-std-serializers": {
"version": "4.0.0"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"postcss": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"version": "8.4.14",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"requires": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"nanoid": "^3.3.4",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"picocolors": "^1.0.0",
"source-map-js": "^1.0.2"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"postgres-array": {
"version": "2.0.0"
},
"postgres-bytea": {
"version": "1.0.0"
},
"postgres-date": {
"version": "1.0.7"
},
"postgres-interval": {
"version": "1.2.0",
"requires": {
"xtend": "^4.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"prelude-ls": {
"version": "1.2.1",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"prepend-http": {
"version": "2.0.0",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"prettier": {
"version": "2.5.1",
"dev": true
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"prettier-linter-helpers": {
"version": "1.0.0",
"dev": true,
"requires": {
"fast-diff": "^1.1.2"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"process": {
"version": "0.10.1"
},
"process-warning": {
"version": "1.0.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"proxy-addr": {
"version": "2.0.7",
"requires": {
"forwarded": "0.2.0",
"ipaddr.js": "1.9.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"pstree.remy": {
"version": "1.1.8",
"dev": true
},
"pump": {
"version": "3.0.0",
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"punycode": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.1.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"pupa": {
"version": "2.1.1",
"dev": true,
"requires": {
"escape-goat": "^2.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"qs": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "6.9.6"
},
"queue-microtask": {
"version": "1.2.3"
},
"quick-format-unescaped": {
"version": "4.0.4"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"randombytes": {
"version": "2.1.0",
"dev": true,
"requires": {
"safe-buffer": "^5.1.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"range-parser": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"raw-body": {
"version": "2.4.2",
"requires": {
"bytes": "3.1.1",
"http-errors": "1.8.1",
"iconv-lite": "0.4.24",
"unpipe": "1.0.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"rc": {
"version": "1.2.8",
"dev": true,
"requires": {
"deep-extend": "^0.6.0",
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
},
"dependencies": {
"ini": {
"version": "1.3.8",
"dev": true
},
"strip-json-comments": {
"version": "2.0.1",
"dev": true
}
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"readable-stream": {
"version": "3.6.0",
"requires": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"readdirp": {
"version": "3.6.0",
"dev": true,
"requires": {
"picomatch": "^2.2.1"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"real-require": {
"version": "0.1.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"regexpp": {
"version": "3.2.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"registry-auth-token": {
"version": "4.2.1",
"dev": true,
"requires": {
"rc": "^1.2.8"
}
},
"registry-url": {
"version": "5.1.0",
"dev": true,
"requires": {
"rc": "^1.2.8"
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"require-directory": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.1.1"
},
"require-from-string": {
"version": "2.0.2"
},
"require-in-the-middle": {
"version": "5.1.0",
"requires": {
"debug": "^4.1.1",
"module-details-from-path": "^1.0.3",
"resolve": "^1.12.0"
},
"dependencies": {
"debug": {
"version": "4.3.4",
"requires": {
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2"
}
}
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"resolve": {
"version": "1.22.0",
"requires": {
"is-core-module": "^2.8.1",
"path-parse": "^1.0.7",
"supports-preserve-symlinks-flag": "^1.0.0"
}
},
"resolve-from": {
"version": "4.0.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"responselike": {
"version": "1.0.2",
"dev": true,
"requires": {
"lowercase-keys": "^1.0.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"ret": {
"version": "0.2.2"
},
"reusify": {
"version": "1.0.4"
},
"rfdc": {
"version": "1.3.0"
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"rimraf": {
"version": "3.0.2",
"dev": true,
"requires": {
"glob": "^7.1.3"
}
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"rollup": {
"version": "2.67.2",
"dev": true,
"requires": {
"fsevents": "~2.3.2"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"safe-buffer": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "5.2.1"
},
"safe-regex2": {
"version": "2.0.0",
"requires": {
"ret": "~0.2.0"
}
},
"safe-stable-stringify": {
"version": "2.3.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
"safer-buffer": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.1.2"
},
"secure-json-parse": {
"version": "2.4.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"secure-keys": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.0"
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"semver": {
"version": "6.3.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"semver-diff": {
"version": "3.1.1",
"dev": true,
"requires": {
"semver": "^6.3.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"semver-store": {
"version": "0.3.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"send": {
"version": "0.17.2",
"requires": {
"debug": "2.6.9",
"depd": "~1.1.2",
"destroy": "~1.0.4",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"fresh": "0.5.2",
"http-errors": "1.8.1",
"mime": "1.6.0",
"ms": "2.1.3",
"on-finished": "~2.3.0",
"range-parser": "~1.2.1",
"statuses": "~1.5.0"
},
"dependencies": {
"ms": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "2.1.3"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
}
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"serialize-javascript": {
"version": "6.0.0",
"dev": true,
"requires": {
"randombytes": "^2.1.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"serve-static": {
"version": "1.14.2",
"requires": {
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"parseurl": "~1.3.3",
"send": "0.17.2"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"set-cookie-parser": {
"version": "2.5.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"setprototypeof": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.2.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"shebang-command": {
"version": "2.0.0",
"dev": true,
"requires": {
"shebang-regex": "^3.0.0"
}
},
"shebang-regex": {
"version": "3.0.0",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"shimmer": {
"version": "1.2.1"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"signal-exit": {
"version": "3.0.7",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"sonic-boom": {
"version": "2.8.0",
"requires": {
"atomic-sleep": "^1.0.0"
}
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"source-map-js": {
"version": "1.0.2",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"split2": {
"version": "4.1.0"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"statuses": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.5.0"
},
"stream-shift": {
"version": "1.0.1"
},
"string_decoder": {
"version": "1.3.0",
"requires": {
"safe-buffer": "~5.2.0"
}
},
"string-similarity": {
"version": "4.0.4"
},
"string-template": {
"version": "0.2.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"string-width": {
"version": "4.2.3",
"requires": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"strip-ansi": {
"version": "6.0.1",
"requires": {
"ansi-regex": "^5.0.1"
}
},
"strip-json-comments": {
"version": "3.1.1",
"dev": true
},
"supports-color": {
"version": "7.2.0",
Remove `matrix-bot-sdk` usage in tests (#15) Remove `matrix-bot-sdk` usage in tests because it didn't have timestamp massaging `?ts` and it's not really necessary to rely on since we can just call the API directly 🤷. `matrix-bot-sdk` is also very annoying having to build rust crypto packages. We're now using direct `fetch` requests against the Matrix API and lightweight `client` object. All 3 current tests pass ✅
2022-06-09 19:44:57 -06:00
"dev": true,
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"requires": {
"has-flag": "^4.0.0"
}
},
"supports-preserve-symlinks-flag": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.0"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"text-table": {
"version": "0.2.0",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"thread-stream": {
"version": "0.15.2",
"requires": {
"real-require": "^0.1.0"
}
},
"thriftrw": {
"version": "3.12.0",
"requires": {
"bufrw": "^1.3.0",
"error": "7.0.2",
"long": "^2.4.0"
}
},
"tiny-lru": {
"version": "8.0.2"
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"to-readable-stream": {
"version": "1.0.0",
"dev": true
},
"to-regex-range": {
"version": "5.0.1",
"dev": true,
"requires": {
"is-number": "^7.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"toidentifier": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.1"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"touch": {
"version": "3.1.0",
"dev": true,
"requires": {
"nopt": "~1.0.10"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"tr46": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.0.3"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"type-check": {
"version": "0.4.0",
"dev": true,
"requires": {
"prelude-ls": "^1.2.1"
}
},
"type-fest": {
"version": "0.20.2",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"type-is": {
"version": "1.6.18",
"requires": {
"media-typer": "0.3.0",
"mime-types": "~2.1.24"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"typedarray-to-buffer": {
"version": "3.1.5",
"dev": true,
"requires": {
"is-typedarray": "^1.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"uhyphen": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "0.1.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"undefsafe": {
"version": "2.0.5",
"dev": true
},
"unique-string": {
"version": "2.0.0",
"dev": true,
"requires": {
"crypto-random-string": "^2.0.0"
}
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"unpipe": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.0"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"update-notifier": {
"version": "5.1.0",
"dev": true,
"requires": {
"boxen": "^5.0.0",
"chalk": "^4.1.0",
"configstore": "^5.0.1",
"has-yarn": "^2.1.0",
"import-lazy": "^2.1.0",
"is-ci": "^2.0.0",
"is-installed-globally": "^0.4.0",
"is-npm": "^5.0.0",
"is-yarn-global": "^0.3.0",
"latest-version": "^5.1.0",
"pupa": "^2.1.1",
"semver": "^7.3.4",
"semver-diff": "^3.1.1",
"xdg-basedir": "^4.0.0"
},
"dependencies": {
"semver": {
"version": "7.3.5",
"dev": true,
"requires": {
"lru-cache": "^6.0.0"
}
}
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"uri-js": {
"version": "4.4.1",
"requires": {
"punycode": "^2.1.0"
}
},
Link calendar days
2022-02-16 18:58:32 -07:00
"url-join": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "4.0.1"
Link calendar days
2022-02-16 18:58:32 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"url-parse-lax": {
"version": "3.0.0",
"dev": true,
"requires": {
"prepend-http": "^2.0.0"
}
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"util-deprecate": {
"version": "1.0.2"
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"utils-merge": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.1"
},
"uuid": {
"version": "8.3.2"
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"v8-compile-cache": {
"version": "2.3.0",
"dev": true
},
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
"vary": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.1.2"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"vite": {
Fix nodemon not being able to watch for changes because vite is interfering (#11) We use `vite@2.9.6` because `vite>=2.9.7` is interfering with `nodemon`, see https://github.com/vitejs/vite/issues/8492 This means that when using `npm run start-dev` -> [`start-dev.js`](https://github.com/matrix-org/matrix-public-archive/blob/40f9d2ea5afb74c4f04030fb1a643fcd803a70e7/server/start-dev.js), `nodemon` wasn't restarting when a change was made.
2022-06-07 13:56:46 -06:00
"version": "2.9.6",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"dev": true,
"requires": {
Update to work with latest `hydrogen-view-sdk@0.0.12` (#10) Get this project running again after a few months of changes from `hydrogen-view-sdk` and now finally after https://github.com/vector-im/hydrogen-web/pull/693 merged to make the SDK friendly to locally link and develop on.
2022-06-06 17:58:45 -06:00
"esbuild": "^0.14.27",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"fsevents": "~2.3.2",
Fix nodemon not being able to watch for changes because vite is interfering (#11) We use `vite@2.9.6` because `vite>=2.9.7` is interfering with `nodemon`, see https://github.com/vitejs/vite/issues/8492 This means that when using `npm run start-dev` -> [`start-dev.js`](https://github.com/matrix-org/matrix-public-archive/blob/40f9d2ea5afb74c4f04030fb1a643fcd803a70e7/server/start-dev.js), `nodemon` wasn't restarting when a change was made.
2022-06-07 13:56:46 -06:00
"postcss": "^8.4.12",
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"resolve": "^1.22.0",
"rollup": "^2.59.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"webidl-conversions": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "3.0.1"
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
},
"whatwg-url": {
"version": "5.0.0",
"requires": {
"tr46": "~0.0.3",
"webidl-conversions": "^3.0.0"
}
},
"which": {
"version": "2.0.2",
"dev": true,
"requires": {
"isexe": "^2.0.0"
}
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"widest-line": {
"version": "3.1.0",
"dev": true,
"requires": {
"string-width": "^4.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"word-wrap": {
"version": "1.2.3",
"dev": true
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"workerpool": {
"version": "6.2.0",
"dev": true
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"wrap-ansi": {
"version": "7.0.0",
"requires": {
"ansi-styles": "^4.0.0",
"string-width": "^4.1.0",
"strip-ansi": "^6.0.0"
}
},
Fetch and render from homeserver
2022-02-07 18:55:11 -07:00
"wrappy": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "1.0.2"
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
},
"write-file-atomic": {
"version": "3.0.3",
"dev": true,
"requires": {
"imurmurhash": "^0.1.4",
"is-typedarray": "^1.0.0",
"signal-exit": "^3.0.2",
"typedarray-to-buffer": "^3.1.5"
}
},
"xdg-basedir": {
"version": "4.0.0",
"dev": true
},
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"xorshift": {
"version": "1.2.0"
},
"xtend": {
"version": "4.0.2"
},
WIP: start of tests
2022-02-22 15:06:29 -07:00
"y18n": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "5.0.8"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"yallist": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "4.0.0"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"yargs": {
"version": "16.2.0",
"requires": {
"cliui": "^7.0.2",
"escalade": "^3.1.1",
"get-caller-file": "^2.0.5",
"require-directory": "^2.1.1",
"string-width": "^4.2.0",
"y18n": "^5.0.5",
"yargs-parser": "^20.2.2"
}
},
"yargs-parser": {
OpenTelemetry tracing so we can see spans where the app is taking time (#27) OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26
2022-07-14 10:08:50 -06:00
"version": "20.2.4"
WIP: start of tests
2022-02-22 15:06:29 -07:00
},
"yargs-unparser": {
"version": "2.0.0",
"dev": true,
"requires": {
"camelcase": "^6.0.0",
"decamelize": "^4.0.0",
"flat": "^5.0.2",
"is-plain-obj": "^2.1.0"
}
},
"yocto-queue": {
"version": "0.1.0",
"dev": true
Strip out PoC pieces (just leave the SSR stuff)
2022-02-05 03:35:02 -07:00
}
}
}