Matrix-Mirrors/mjolnir
1
0
Fork 0
mirror of https://github.com/matrix-org/mjolnir.git synced 2024-10-01 01:36:06 -04:00
Code Issues Packages Projects Releases Wiki Activity
gnuxie/reverting-since
mjolnir/package.json

49 lines
1.7 KiB
JSON
Raw Permalink Normal View History

Absolute bare minimum for a bot
2019-09-25 22:13:20 -04:00
{
"name": "mjolnir",
v1.4.1
2022-03-21 10:28:21 -04:00
"version": "1.4.1",
Absolute bare minimum for a bot
2019-09-25 22:13:20 -04:00
"description": "A moderation tool for Matrix",
"main": "lib/index.js",
"repository": "git@github.com:matrix-org/mjolnir.git",
"author": "The Matrix.org Foundation C.I.C.",
"license": "Apache-2.0",
"private": true,
"scripts": {
"build": "tsc",
Fix the test script `yarn test:manual` and add it to tsconfig (#234) * Add test:manual launch script to tsconfig this is so we won't keep breaking it
2022-02-24 09:46:15 -05:00
"postbuild": "rm -rf lib/test/ && cp -r lib/src/* lib/ && rm -rf lib/src/",
Make the [un]ban command smarter Fixes https://github.com/matrix-org/mjolnir/issues/11
2019-11-13 23:38:19 -05:00
"lint": "tslint --project ./tsconfig.json -t stylish",
Let's make sure that we can still check for errors with concise error handling
2022-01-06 06:19:19 -05:00
"start:dev": "yarn build && node --async-stack-traces lib/index.js",
make yarn test only runs unit tests for now while we sortout CI setup
2021-09-27 07:38:43 -04:00
"test": "ts-mocha --project ./tsconfig.json test/commands/**/*.ts",
Let's make sure that we can still check for errors with concise error handling
2022-01-06 06:19:19 -05:00
"test:integration": "NODE_ENV=harness ts-mocha --async-stack-traces --require test/integration/fixtures.ts --project ./tsconfig.json \"test/integration/**/*Test.ts\"",
Change antispam Python module verison with mjolnir version. (#264) The reason we want this is so that people do not forget to change the version number in the synapse module. The precedent is that the version number has been 0.1.0 since the begging until now. While this solution does mean that there may be new version of the module where nothing has actually changed, this is still better than not changing the version at all. Another version scheme for the module would be inconsistent to the git repository tags and that has the potential to cause much more confusion than "blank" version bumps. If this is a problem, then antispam must be extracted to another repository. In order to test this, run `yarn version --patch` observe the changes with `git log` and `git diff HEAD~`, then YOU MUST delete the tag with `git tag --delete vd.d.d` when you are finished. * more robust
2022-04-12 11:36:35 -04:00
"test:manual": "NODE_ENV=harness ts-node test/integration/manualLaunchScript.ts",
"version": "sed -i '/# version automated/s/[0-9][0-9]*\\.[0-9][0-9]*\\.[0-9][0-9]*/'$npm_package_version'/' synapse_antispam/setup.py && git add synapse_antispam/setup.py && cat synapse_antispam/setup.py"
Absolute bare minimum for a bot
2019-09-25 22:13:20 -04:00
},
"devDependencies": {
enable noImplicitAny (#209)
2022-02-02 07:43:05 -05:00
"@types/config": "0.0.41",
Update package.json and yarn.lock to include harness dependencies.
2021-09-09 11:40:12 -04:00
"@types/crypto-js": "^4.0.2",
enable noImplicitAny (#209)
2022-02-02 07:43:05 -05:00
"@types/html-to-text": "^8.0.1",
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38
2021-10-07 08:42:08 -04:00
"@types/jsdom": "^16.2.11",
Replace shutdown_room API with DELETE /_synapse/admin/v1/rooms/<room_id> - Resolves #76, closes #96 As per https://github.com/matrix-org/synapse/issues/9052, shutdown_room is going away, to be replaced with DELETE /_synapse/admin/v1/rooms/<room_id>.
2021-07-28 04:56:50 -04:00
"@types/mocha": "^9.0.0",
Update package.json and yarn.lock to include harness dependencies.
2021-09-09 11:40:12 -04:00
"@types/node": "^16.7.10",
"crypto-js": "^4.1.1",
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38
2021-10-07 08:42:08 -04:00
"eslint": "^7.32",
Update packages
2021-07-01 15:45:28 -04:00
"expect": "^27.0.6",
"mocha": "^9.0.1",
"ts-mocha": "^8.0.0",
"tslint": "^6.1.3",
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38
2021-10-07 08:42:08 -04:00
"typescript": "^4.3.5",
"typescript-formatter": "^7.2"
Absolute bare minimum for a bot
2019-09-25 22:13:20 -04:00
},
"dependencies": {
Update packages
2021-07-01 15:45:28 -04:00
"config": "^3.3.6",
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38
2021-10-07 08:42:08 -04:00
"express": "^4.17",
Give the ability to moderators to react quickly to /report abuse reports. (#137)
2021-11-09 07:15:49 -05:00
"html-to-text": "^8.0.0",
Update packages
2021-07-01 15:45:28 -04:00
"js-yaml": "^4.1.0",
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38
2021-10-07 08:42:08 -04:00
"jsdom": "^16.6.0",
A room Protection designed to measure lag in a room (#217)
2022-02-24 07:43:31 -05:00
"matrix-bot-sdk": "^0.5.19",
Revert "New command `!mjolnir since <date or duration> <kick | ban | show> <limit> [reason] [...rooms]` (#238)" This reverts commit e05616b327380b2d1058ee7795b338fc3185b71a. We are reverting the since command for multiple reasons. 1. The roomMemberTest that this commit brings has an `it` block ("RoomMemberManager counts correctly when we actually join/leave/get banned from the room") that now fails in an infinite loop and we struggle to understand how it ever passed. > essentially they assert that Mjolnir is in the room here https://github.com/matrix-org/mjolnir/blob/main/test/integration/roomMembersTest.ts#L303 Which is great, but they've never joined it or have been invited. https://github.com/matrix-org/mjolnir/blob/main/test/integration/roomMembersTest.ts#L302 but then we also assert that there's only one person in the room, but this can't be Mjolnir because Mjolnir didn't create these rooms https://github.com/matrix-org/mjolnir/blob/main/test/integration/roomMembersTest.ts#L273, yet they're checking that Mjolnir is indeed there. The loop in question is also over complicated and hard to read https://github.com/matrix-org/mjolnir/pull/225/files#diff-67e09dce96f975b2df641d3c600f60f48aeeb9e54a472b612bce90535b4aa0e4R285-R295 Should have been written like this. ``` while(!roomIds.each(roomId => this.mjolnir.protectedRooms[roomId])) { await new Promise(resolve => setTimeout(resolve, 1_000)); } ``` 2. The RoomMemberManager is broken even after fixing the test (fixing so that it fails "normally" without getting caught in the loop by changing the setup code) and we have decided is not worth fixing yet. This is because it is complex & the manager only knows about joins that have happened since Mjolnir has started syncing, this has proven un-initiative to Mjolnir users already. Possible solutions are using the planned the full rolling room member/state cache (https://github.com/matrix-org/mjolnir/issues/273) or using `/messages` with a filter for member events for the `!since` command, since `/messages` is "chronologically" ordered.
2022-04-29 07:10:09 -04:00
"parse-duration": "^1.0.2"
Bump minimum node version to >=14 Needed to merge https://github.com/matrix-org/mjolnir/pull/186 & node 12 is approaching EOL.
2022-01-18 11:33:30 -05:00
},
"engines": {
"node": ">=14.0.0"
Absolute bare minimum for a bot
2019-09-25 22:13:20 -04:00
}
}
Reference in New Issue Copy Permalink