Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -195,56 +195,56 @@
"@actions/core": "^3.0.1",
"@actions/github": "^9.1.1",
"@babel/helpers": "^8.0.0",
"@eslint/eslintrc": "^3.3.5",
"@eslint/eslintrc": "^3.3.6",
"@eslint/js": "^10.0.1",
"@msgpack/msgpack": "^3.1.3",
"@openfeature/core": "^1.11.0",
"@openfeature/server-sdk": "~1.22.0",
"@openfeature/core": "^1.12.0",
"@openfeature/server-sdk": "~1.23.0",
"@stylistic/eslint-plugin": "^5.10.0",
"@types/mocha": "^10.0.10",
"@types/node": "^18.19.106",
"@types/sinon": "^22.0.0",
"@vercel/nft": "^1.10.2",
"@yarnpkg/lockfile": "^1.1.0",
"axios": "^1.18.1",
"axios": "^1.19.0",
"benchmark": "^2.1.4",
"body-parser": "^2.3.0",
"bun": "1.3.14",
"c8": "^12.0.0",
"codeowners-audit": "^2.9.0",
"eslint": "^10.5.0",
"eslint-plugin-cypress": "^6.4.2",
"eslint": "^10.8.0",
"eslint-plugin-cypress": "^6.4.3",
"eslint-plugin-import-x": "^4.16.2",
"eslint-plugin-jsdoc": "^63.0.12",
"eslint-plugin-jsdoc": "^63.3.2",
"eslint-plugin-mocha": "^11.3.0",
"eslint-plugin-n": "^18.2.1",
"eslint-plugin-n": "^18.2.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid bumping eslint-plugin-n without fixing callbacks

With eslint-plugin-n at 18.2.2, the enabled n/no-callback-literal rule now also reports object/array/template literals in callback/cb error positions, and this repo still has direct object calls such as callback({ statusCode: 200, ... }) in packages/dd-trace/test/opentelemetry/traces.spec.js:80 and cb({ [targetClass]: TargetClass }) in packages/datadog-instrumentations/test/openai-lifecycle.spec.js:126. Since the root lint config keeps this rule as error, npm run lint will fail after this dependency bump unless those existing call sites are fixed or explicitly exempted.

Useful? React with 👍 / 👎.

"eslint-plugin-promise": "^7.3.0",
"eslint-plugin-sonarjs": "^4.2.0",
"eslint-plugin-unicorn": "^73.0.0",
"express": "^5.1.0",
"glob": "^10.4.5",
"globals": "^17.7.0",
"globals": "^17.8.0",
"graphql": "*",
"husky": "^9.1.7",
"istanbul-lib-report": "^3.0.0",
"istanbul-reports": "^3.0.2",
"jsonc-parser": "^3.3.1",
"jszip": "^3.10.1",
"minimatch": "^10.2.5",
"minimatch": "^10.2.6",
"mocha": "^11.7.6",
"mocha-junit-reporter": "^2.2.1",
"mocha-multi-reporters": "^1.5.1",
"multer": "^2.2.0",
"nock": "^14.0.16",
"nock": "^14.0.17",
"node-preload": "^0.2.1",
"nyc": "^18.0.0",
"octokit": "^5.0.3",
"p-limit": "^7.2.0",
"p-limit": "^7.3.1",
"proxyquire": "^2.1.3",
"retry": "^0.13.1",
"semifies": "^1.0.0",
"semver": "^7.8.5",
"sinon": "^22.0.0",
"sinon": "^22.1.0",
"source-map-support": "^0.5.21",
"test-exclude": "^8.0.0",
"tiktoken": "^1.0.21",
Expand Down
Loading
Loading