Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging with Pino #13

Closed
ghost opened this issue May 4, 2022 · 1 comment · Fixed by #8
Closed

Logging with Pino #13

ghost opened this issue May 4, 2022 · 1 comment · Fixed by #8
Labels
P0 Highest priority TASK Task

Comments

@ghost
Copy link

ghost commented May 4, 2022

Add Pino Logger and replace all the console statements with logger (info, warn, debug, error)

@ghost ghost self-assigned this May 4, 2022
@ghost ghost added P0 Highest priority TASK Task labels May 4, 2022
@ghost ghost linked a pull request May 5, 2022 that will close this issue
@ghost
Copy link
Author

ghost commented May 5, 2022

  • pino logging added. Integrated express-pino-logger
  • pino-debug is pending. The package is throwing this error
    error TS7016: Could not find a declaration file for module 'pino-debug'. '/home/gurjot/mindgrep/gs_project_template/gs_service/node_modules/pino-debug/index.js' implicitly has an 'any' type. Try npm i --save-dev @types/pino-debugif it exists or add a new declaration (.d.ts) file containingdeclare module 'pino-debug';`

1 import pinoDebug from 'pino-debug'
~~~~~~~~~~~~

Found 1 error in build/core/logger.ts:1
npm i --save-dev @types/pino-debug
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types%2fpino-debug - Not found
npm ERR! 404
npm ERR! 404 '@types/pino-debug@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
`

@ghost ghost closed this as completed Oct 7, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Highest priority TASK Task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants