feat: create consola instance to improve logging
#264
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shivarm
commented
Apr 1, 2025
Comment on lines
+4
to
+6
| defaults: { | ||
| tag: 'Vidur', | ||
| }, |
Member
Author
|
I have added tag so current log look like and it give us clear structure [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 |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
improve logging sprint with consola, see the current following logs for vidur
yarn dev yarn run v1.22.22 $ nuxt dev Nuxt 3.16.1 with Nitro 2.11.8 nuxi 1:12:53 pm 1:12:53 pm ➜ Local: http://localhost:3001/ ➜ Network: use --host to expose ℹ Using default Tailwind CSS file nuxt:tailwindcss 1:12:55 pm ℹ Using zod with vee-validate 1:12:55 pm ➜ DevTools: press Shift + Alt + D in the browser (v2.3.2) 1:12:55 pm ℹ Running with compatibility version 4 nuxt 1:12:56 pm ✔ Vite client built in 64ms 1:12:58 pm ✔ Vite server built in 1412ms 1:12:59 pm ✔ Nuxt Nitro server built in 4889ms nitro 1:13:06 pm ℹ Vite client warmed up in 5ms 1:13:06 pm ℹ Seeding Database ◐ Connecting to PostgreSQL ℹ Vite server warmed up in 2738ms 1:13:09 pm ✔ Connected to PostgreSQL ℹ Current Seed Version 3 Total Seed Versions 3 ℹ Mounting files on ./.data ℹ Mounting local driver. ℹ Seeding Cache ℹ Reusing existing database connection. ◐ Checking if access key present ✔ Access key not found, it means vidur instance is setup ℹ Reusing existing database connection. ℹ [Tue Apr 01 2025 13:13:12 GMT+0530 (India Standard Time)]: Marked 0 postings as expired. ℹ [PUBLIC] postings page found 0 postings. ℹ grabbing asset ce66f077-c7da-45a6-b49c-97ab25b40e57