vczb / lighthouse-reporter Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 6.0 626 KB

Generate lighthouse reports and save it in a mongo database.

License: MIT License

TypeScript 100.00%

api hacktoberfest lighthouse mongodb nodejs seo

lighthouse-reporter's Introduction

profile . repositories . public learning . sponsor . linked in

lighthouse-reporter's People

Contributors

Stargazers

Watchers

Forkers

mshehu5 yasionfire i-dipanshu avinash2110 guillergood kadar77

lighthouse-reporter's Issues

Protect route attributes with celebrate

use this example as reference: https://github.com/vczb/be-the-hero/blob/master/backend/src/routes.js

Remove unnecessary data from JSON responses

Some responses are returning unnecessary data like "_id" and "__v"

Let's cleanup the response JSON and return only what is needed

In the README we have the API documentation, which should be updated too

Allow multiple reports at same time

Refactor routes to an external file

remove enpoints from server.ts

create a routes.ts file

import it on server.ts

Refactor esmodules imports

some places are using require and others import. make it homogeneous

Protocol "https:" not supported. Expected "http:"

This error occur when dispatch a report

  LH:status Generating results... +3ms
Report is done for https://vczb.github.io/about
Report finished
Report data:
 [
  {
    url: 'https://vczb.github.io/',
    accessibility: 81,
    best: 92,
    performance: 76,
    pwa: 30,
    seo: 98
  },
  {
    url: 'https://vczb.github.io/about',
    accessibility: 71,
    best: 92,
    performance: 67,
    pwa: 20,
    seo: 97
  }
]
TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
    at new NodeError (node:internal/errors:371:5)
    at new ClientRequest (node:_http_client:158:11)
    at Object.request (node:http:96:10)
    at /home/vini/src/lighthouse-reporter/src/app/controllers/trigger.controller.ts:111:28
    at step (/home/vini/src/lighthouse-reporter/src/app/controllers/trigger.controller.ts:33:23)
    at Object.next (/home/vini/src/lighthouse-reporter/src/app/controllers/trigger.controller.ts:14:53)
    at fulfilled (/home/vini/src/lighthouse-reporter/src/app/controllers/trigger.controller.ts:5:58)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 'ERR_INVALID_PROTOCOL'
}
[nodemon] app crashed - waiting for file changes before starting...

Global Error Handler

I would create a folder which contains "Global Error Handler". Can you assign this issue to me?

Add support to webhook callback after trigger

should add a callback url on trigger document
should execute a POST http request after the trigger finish to the callback url

Catch Async Function

In order to get rid of multiple try-catch blocks, I want to create a file under the utilities folder to achieve this. If it is a good idea, can you assign this to me? Thank you.

Create project LOGO

Design a logo.
Export the logo as SVG and PNG on the root directory (name logo.svg and logo.png)

Create user controller ( edit/delete)

Edit current user ( logged )
Delete current user ( should delete in cascade triggers and reports )

Create edit trigger flow

route
controller
documentation

Create delete trigger flow

Add to routes
Add to controller
Add to docs ( readme )

Update contributing section on README

Should add clear information about how to contribute. Fork, clone, create a branch, etc... Also, is very important explain how to update your forked repository after some changes ( with rebase ).

Fell free to research on others repositories and google for examples.

thanks

any question I'm available

Add unit tests with jest

BUG - Error generating report in production

Sep 3 08:49:11 PM  (node:52) UnhandledPromiseRejectionWarning: Error
Sep 3 08:49:11 PM      at new LauncherError (/opt/render/project/src/node_modules/chrome-launcher/src/utils.ts:31:18)
Sep 3 08:49:11 PM      at new ChromePathNotSetError (/opt/render/project/src/node_modules/chrome-launcher/dist/utils.js:33:9)
Sep 3 08:49:11 PM      at Object.linux (/opt/render/project/src/node_modules/chrome-launcher/src/chrome-finder.ts:153:11)
Sep 3 08:49:11 PM      at Function.getFirstInstallation (/opt/render/project/src/node_modules/chrome-launcher/src/chrome-launcher.ts:192:61)
Sep 3 08:49:11 PM      at Launcher.launch (/opt/render/project/src/node_modules/chrome-launcher/src/chrome-launcher.ts:262:37)
Sep 3 08:49:11 PM      at Object.launch (/opt/render/project/src/node_modules/chrome-launcher/src/chrome-launcher.ts:73:18)
Sep 3 08:49:11 PM      at /opt/render/project/src/src/services/lighthouse.ts:5:39
Sep 3 08:49:11 PM      at step (/opt/render/project/src/src/services/lighthouse.ts:33:23)
Sep 3 08:49:11 PM      at Object.next (/opt/render/project/src/src/services/lighthouse.ts:14:53)
Sep 3 08:49:11 PM      at /opt/render/project/src/src/services/lighthouse.ts:8:71
Sep 3 08:49:11 PM  (Use `node --trace-warnings ...` to show where the warning was created)
Sep 3 08:49:11 PM  (node:52) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Create a Social preview image

File should be located on the root dir and named as Social.png
Should be PNG
Can be equal to Logo or not ( if not follow the same styled-guide )
Follow the width / height as bellow