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.json

62 lines
1.9 KiB
JSON
Raw Normal View History

main2 working from static event JSON
2022-02-01 20:39:23 -07:00
{
"name": "matrix-public-archive",
"version": "0.0.0",
Add Apache 2.0 license (#55)
2022-08-30 17:35:36 -06:00
"license": "Apache-2.0",
"repository": {
"type": "git",
"url": "https://github.com/matrix-org/matrix-public-archive"
},
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
"scripts": {
Fix lints
2022-02-15 20:33:31 -07:00
"lint": "eslint **/*.js",
Rename to build-scripts to it appears in GitHub file finder (#166) It seems like the `build/` directory is ignored in the GitHub file finder as a sane default for people who put compiled assets there. `build-scripts/` probably makes more sense anyway
2023-04-07 12:17:46 -06:00
"build": "node ./build-scripts/do-client-build.js",
Containerize app (make a Docker image for `matrix-public-archive`) (#22) Containerize app (make a Docker image for `matrix-public-archive`) ``` ghcr.io/matrix-org/matrix-public-archive/matrix-public-archive ``` ... with a variety of tags! Packages viewable on https://github.com/matrix-org/matrix-public-archive/pkgs/container/matrix-public-archive%2Fmatrix-public-archive
2022-06-15 01:28:18 -06:00
"start": "node server/server.js",
"start-dev": "node server/start-dev.js",
Add a way to select time of day (#139) - Fix https://github.com/matrix-org/matrix-public-archive/issues/7 - A URL with time looks like - `/r/too-many-messages-on-day:my.synapse.server/date/2022/11/16T23:59` - Or when more precision is required (seconds): `/r/too-many-messages-on-day:my.synapse.server/date/2022/11/16T23:59:59` - Add new custom time picker/scrubber (pictured below) with momentum scrubbing - Native built-in `<input type="time">` for easier picking if you prefer that and accessibility. - Uses localized time strings - Design inspired by Thiago Sanchez's *Time Zone Translate* concept, https://dribbble.com/shots/14590546-Time-Zone-Translate
2023-04-05 03:25:31 -06:00
"test": "npm run mocha -- test/**/*-tests.js --timeout 15000",
Follow tombstone and predecessor history (#167) Fix https://github.com/matrix-org/matrix-public-archive/issues/59 Other updates: - Update tests to use `/roomid/room1/date/2022/01/03` format instead of trying to retrofit the weird alias stuff on there. Which also makes the fancy to actual URL utilities much more simple. - Update to specify `archiveMessageLimit` in the test case because pages have different number of events depending on if we are against a boundary, hidden events, etc.
2023-04-19 00:26:15 -06:00
"test-e2e-interactive": "npm run mocha -- test/e2e-tests.js --timeout 15000 --bail --interactive",
Add npm run start-dev to build vite and run server at once
2022-02-15 16:17:14 -07:00
"nodemon": "nodemon",
Production ready build (#175) - Rename `public` -> `client` so it doesn't get copied automagically as-is (without hashes which we want for cache busting), https://vitejs.dev/guide/assets.html#the-public-directory - We still build the version files to `public/` so their copied as-is and Vite handles it for us (so we can use `emptyOutDir`) - Use a multiple entrypoint `.js` Vite build so things can be more intelligently bundled and take less time - We aren't using library mode because it doesn't minify or bundle assets - Using hash asset tags for cache busting. Hash of the file included in the file name - We lookup these hashed assets from `manifest.json` that Vite builds (https://vitejs.dev/guide/backend-integration.html) to serve and preload - In terms of optimized bundles, I know the current output isn't great now but will have to opt to fix that up separately in the future. Tracked by https://github.com/matrix-org/matrix-public-archive/issues/176
2023-04-24 22:50:53 -06:00
"gulp": "gulp",
Fix lints
2022-02-15 20:33:31 -07:00
"vite": "vite",
WIP: start of tests
2022-02-22 15:06:29 -07:00
"mocha": "mocha",
Fix lints
2022-02-15 20:33:31 -07:00
"eslint": "eslint",
"prettier": "prettier"
},
Link calendar days
2022-02-16 18:58:32 -07:00
"engines": {
"node": ">=16.0.0"
Re-mount on client to get JS interactivity
2022-02-15 00:33:16 -07:00
},
main2 working from static event JSON
2022-02-01 20:39:23 -07:00
"devDependencies": {
Follow tombstone and predecessor history (#167) Fix https://github.com/matrix-org/matrix-public-archive/issues/59 Other updates: - Update tests to use `/roomid/room1/date/2022/01/03` format instead of trying to retrofit the weird alias stuff on there. Which also makes the fancy to actual URL utilities much more simple. - Update to specify `archiveMessageLimit` in the test case because pages have different number of events depending on if we are against a boundary, hidden events, etc.
2023-04-19 00:26:15 -06:00
"chalk": "^4.1.2",
Update linting so we don't need omit the context filling name of some variables (#165) `"no-unused-vars": ["error", { "destructuredArrayIgnorePattern": "^_" }],` was only [introduced in `eslint@8.11.0`](https://github.com/eslint/eslint/blob/0fd6bb213ad2de77543c936eda21501653182e52/CHANGELOG.md) so we had to update
2023-04-07 12:01:20 -06:00
"eslint": "^8.37.0",
"eslint-config-prettier": "^8.8.0",
Migrate from `eslint-plugin-node` to `eslint-plugin-n` (#179)
2023-04-24 23:39:59 -06:00
"eslint-plugin-n": "^15.7.0",
Update linting so we don't need omit the context filling name of some variables (#165) `"no-unused-vars": ["error", { "destructuredArrayIgnorePattern": "^_" }],` was only [introduced in `eslint@8.11.0`](https://github.com/eslint/eslint/blob/0fd6bb213ad2de77543c936eda21501653182e52/CHANGELOG.md) so we had to update
2023-04-07 12:01:20 -06:00
"eslint-plugin-prettier": "^4.2.1",
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",
Update linting so we don't need omit the context filling name of some variables (#165) `"no-unused-vars": ["error", { "destructuredArrayIgnorePattern": "^_" }],` was only [introduced in `eslint@8.11.0`](https://github.com/eslint/eslint/blob/0fd6bb213ad2de77543c936eda21501653182e52/CHANGELOG.md) so we had to update
2023-04-07 12:01:20 -06:00
"prettier": "^2.8.7",
Production ready build (#175) - Rename `public` -> `client` so it doesn't get copied automagically as-is (without hashes which we want for cache busting), https://vitejs.dev/guide/assets.html#the-public-directory - We still build the version files to `public/` so their copied as-is and Vite handles it for us (so we can use `emptyOutDir`) - Use a multiple entrypoint `.js` Vite build so things can be more intelligently bundled and take less time - We aren't using library mode because it doesn't minify or bundle assets - Using hash asset tags for cache busting. Hash of the file included in the file name - We lookup these hashed assets from `manifest.json` that Vite builds (https://vitejs.dev/guide/backend-integration.html) to serve and preload - In terms of optimized bundles, I know the current output isn't great now but will have to opt to fix that up separately in the future. Tracked by https://github.com/matrix-org/matrix-public-archive/issues/176
2023-04-24 22:50:53 -06:00
"vite": "^4.3.1"
main2 working from static event JSON
2022-02-01 20:39:23 -07:00
},
"dependencies": {
Timeout requests and stop processing further (#204) Fix https://github.com/matrix-org/matrix-public-archive/issues/148 Fix https://github.com/matrix-org/matrix-public-archive/issues/40 - Apply timeout middleware to all room directory and room routes - Stop messing with the response after we timeout. Fix https://github.com/matrix-org/matrix-public-archive/issues/148 - This also involves cancelling any `async/await` things like requests in the routes so we throw an abort error instead of continuing on. Fix https://github.com/matrix-org/matrix-public-archive/issues/40 - Also abort the route if we see that the user closed the request before we could respond to them - Bumps minimum supported Node.js version to v18 because we're now using the built-in native `fetch` in Node.js vs `node-fetch`. This gives us the custom `signal.reason` that we aborted with instead of a generic `AbortError`. - This also means we had to add some instrumentation for `fetch` which uses `undici` under the hood. Settled on some unofficial instrumentation: [`opentelemetry-instrumentation-fetch-node`](https://www.npmjs.com/package/opentelemetry-instrumentation-fetch-node)
2023-05-01 23:39:01 -06:00
"@opentelemetry/api": "^1.4.1",
"@opentelemetry/auto-instrumentations-node": "^0.36.6",
"@opentelemetry/context-async-hooks": "^1.12.0",
"@opentelemetry/core": "^1.12.0",
"@opentelemetry/exporter-jaeger": "^1.12.0",
"@opentelemetry/instrumentation": "^0.38.0",
"@opentelemetry/propagator-ot-trace": "^0.26.2",
"@opentelemetry/resources": "^1.12.0",
"@opentelemetry/sdk-trace-base": "^1.12.0",
"@opentelemetry/semantic-conventions": "^1.12.0",
Update linting so we don't need omit the context filling name of some variables (#165) `"no-unused-vars": ["error", { "destructuredArrayIgnorePattern": "^_" }],` was only [introduced in `eslint@8.11.0`](https://github.com/eslint/eslint/blob/0fd6bb213ad2de77543c936eda21501653182e52/CHANGELOG.md) so we had to update
2023-04-07 12:01:20 -06:00
"cors": "^2.8.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
"dompurify": "^2.3.9",
Move escape-string-regexp to a normal dep since we use it on the server (#178)
2023-04-24 23:10:01 -06:00
"escape-string-regexp": "^4.0.0",
SSR with linkedom Currently doesn't work because the `window` object doesn't include things like `window.crypto`.
2022-02-03 22:44:49 -07:00
"express": "^4.17.2",
Add safe search filter for NSFW rooms (#208) Fix https://github.com/matrix-org/matrix-public-archive/issues/89
2023-05-03 03:45:33 -06:00
"hydrogen-view-sdk": "npm:@mlm/hydrogen-view-sdk@^0.27.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",
Page-load with the correct homeserver selected (#98) Page-load with the correct homeserver selected (according to `?homeserver`). Fix https://github.com/matrix-org/matrix-public-archive/issues/92 Also makes sure that the `?homeserver` is always available somewhere in the list; whether that be in the available homeserver list or the added homeserver list depending on it someone cleared it out or never had it because they visited from someone else's link.
2022-10-21 01:09:26 -06:00
"linkedom": "^0.14.17",
WIP: Add calendar to right panel
2022-02-14 20:11:55 -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",
Timeout requests and stop processing further (#204) Fix https://github.com/matrix-org/matrix-public-archive/issues/148 Fix https://github.com/matrix-org/matrix-public-archive/issues/40 - Apply timeout middleware to all room directory and room routes - Stop messing with the response after we timeout. Fix https://github.com/matrix-org/matrix-public-archive/issues/148 - This also involves cancelling any `async/await` things like requests in the routes so we throw an abort error instead of continuing on. Fix https://github.com/matrix-org/matrix-public-archive/issues/40 - Also abort the route if we see that the user closed the request before we could respond to them - Bumps minimum supported Node.js version to v18 because we're now using the built-in native `fetch` in Node.js vs `node-fetch`. This gives us the custom `signal.reason` that we aborted with instead of a generic `AbortError`. - This also means we had to add some instrumentation for `fetch` which uses `undici` under the hood. Settled on some unofficial instrumentation: [`opentelemetry-instrumentation-fetch-node`](https://www.npmjs.com/package/opentelemetry-instrumentation-fetch-node)
2023-05-01 23:39:01 -06:00
"opentelemetry-instrumentation-fetch-node": "^1.0.0",
Link calendar days
2022-02-16 18:58:32 -07:00
"url-join": "^4.0.1"
main2 working from static event JSON
2022-02-01 20:39:23 -07:00
}
}