Philipp
076e96f3de
This PR fixes the issue where console monitoring was empty when a specific shard was targeted on the official Screeps server. ### Changes: - **Unified Subscription**: Changed WebSocket subscription path from `shard/console` (invalid) to the global `console` channel. - **Shard Filtering**: Implemented client-side filtering in `handleConsoleEvent` to only display logs matching the targeted shard. - **Precise Timing**: Retained the shard-specific `api.time()` call for accurate tick duration tracking. - **Tests**: Added and updated 48 unit tests verifying the fix and shard filtering logic. - **Distribution**: Rebuilt `dist/index.js` and bumped version to `v0.2.1`. Reviewed-on: #87
24 lines
637 B
JSON
24 lines
637 B
JSON
{
|
|
"name": "screeps-deploy-action",
|
|
"version": "0.2.1",
|
|
"description": "Deploys screeps code to the official game or a private server.",
|
|
"type": "module",
|
|
"main": "index.js",
|
|
"scripts": {
|
|
"start": "node index.js",
|
|
"test": "vitest run --globals --coverage",
|
|
"build": "ncc build index.js -o dist -m --external utf-8-validate --external bufferutil"
|
|
},
|
|
"dependencies": {
|
|
"@actions/artifact": "^1.1.2",
|
|
"@actions/core": "^3.0.0",
|
|
"glob": "^13.0.0",
|
|
"screeps-api": "^1.7.2"
|
|
},
|
|
"devDependencies": {
|
|
"@vercel/ncc": "^0.38.4",
|
|
"@vitest/coverage-v8": "^4.0.16",
|
|
"vitest": "^4.0.16"
|
|
}
|
|
}
|