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

Improve Logging - Sprint #60

Open
5 tasks
amandesai01 opened this issue Aug 8, 2024 · 4 comments
Open
5 tasks

Improve Logging - Sprint #60

amandesai01 opened this issue Aug 8, 2024 · 4 comments
Assignees

Comments

@amandesai01
Copy link
Member

amandesai01 commented Aug 8, 2024

Currently we use IS_DEV flag and raw console.log to log data.

Rather, we can

  • Create a Consola instance in utils/logger.ts #61
  • Create a runtime config to set log-level.
  • Log all basic things (wrapped by IS_DEV) at trace and debug level depending on log.
  • Log all things which are not wrapped by IS_DEV to normal logs.
  • Log all errors to error level.

Open to better / in detailed proposals.

@amandesai01 amandesai01 changed the title Improve Logging Improve Logging - Sprint Aug 8, 2024
@amandesai01 amandesai01 self-assigned this Aug 8, 2024
@amandesai01 amandesai01 pinned this issue Aug 8, 2024
@ameyagidh
Copy link

Can I work on this?

@amandesai01 amandesai01 unpinned this issue Sep 10, 2024
@shivarm
Copy link
Member

shivarm commented Mar 30, 2025

@amandesai01 Worked on this, will open PR .. See the logs

yarn dev
yarn run v1.22.22
$ nuxt dev
Nuxt 3.15.3 with Nitro 2.10.4                                                                                                                                 nuxi 8:11:37 am  
                                                                                                                                                                   8:11:37 am  
  ➜ Local:    http://localhost:3001/
  ➜ Network:  use --host to expose

ℹ Using default Tailwind CSS file                                                                                                                nuxt:tailwindcss 8:11:41 am   
ℹ Using zod with vee-validate                                                                                                                                     8:11:42 am   
  ➜ DevTools: press Shift + Alt + D in the browser (v1.7.0)                                                                                                        8:11:45 am

ℹ Running with compatibility version 4                                                                                                                       nuxt 8:11:47 am
✔ Vite client built in 67ms                                                                                                                                       8:11:52 am
✔ Vite server built in 1242ms                                                                                                                                     8:11:53 am

 WARN  Browserslist: caniuse-lite is outdated. Please run:                                                                                                         8:11:53 am
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme

✔ Nuxt Nitro server built in 3784 ms                                                                                                                        nitro 8:11:58 am
ℹ Vite client warmed up in 4ms                                                                                                                                    8:11:58 am
[Vidur] ℹ Seeding Database
[Vidur] ◐ Connecting to PostgreSQL
ℹ Vite server warmed up in 3421ms                                                                                                                                 8:12:02 am
[Vidur] ✔ Connected to PostgreSQL
[Vidur] ℹ Current Seed Version 3 Total Seed Versions 3
[Vidur] ℹ Mounting files on ./.data
[Vidur] ℹ Mounting local driver.
[Vidur] ℹ Seeding Cache
[Vidur] ℹ Reusing existing database connection.
[Vidur] ◐ Checking if access key present
[Vidur] ℹ Access key not found, it means vidur instance is setup
[Vidur] ℹ Reusing existing database connection.
[Sun Mar 30 2025 08:12:05 GMT+0530 (India Standard Time)]: Marked 0 postings as expired.
[Vidur] ℹ [PUBLIC] postings page found 0 postings.
[Vidur] ℹ grabbing asset ce66f077-c7da-45a6-b49c-97ab25b40e57

@amandesai01
Copy link
Member Author

update the same existing PR, rebase and update

@shivarm
Copy link
Member

shivarm commented Mar 30, 2025

@amandesai01 No, let's create fresh, I don't want to resolve merge-conflicts on Sunday 😀 and also I belive I don't have access to push anyone branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants