Skip to content

feat: add client side performance tracking #248

feat: add client side performance tracking

feat: add client side performance tracking #248

Triggered via pull request February 18, 2024 14:43
Status Failure
Total duration 22s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
build: lib/client/hijack/wrapSubscription.js#L35
The function binding is unnecessary
build
Process completed with exit code 1.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build: lib/client/utils.js#L95
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/environment_variables.js#L7
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/hijack/db.js#L145
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/hijack/wrap_webapp.js#L54
Unexpected require()
build: lib/models/http.js#L104
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/models/http.js#L110
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/models/methods.js#L148
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype
build: lib/models/methods.js#L154
The body of a for-in should be wrapped in an if statement to filter unwanted properties from the prototype