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

Feature Request: Add RHS timestamp support #8

Open
subodhpareek18 opened this issue Jan 19, 2018 · 3 comments
Open

Feature Request: Add RHS timestamp support #8

subodhpareek18 opened this issue Jan 19, 2018 · 3 comments

Comments

@subodhpareek18
Copy link

I am using https://github.com/jaredpalmer/backpack for my backend server and it internally uses the really nice https://github.com/geowarin/friendly-errors-webpack-plugin/

So I looked around and found this package that looks very similar, except for a couple of differences. The one I'm talking about here is to be able to show the timestamp cleanly on the RHS side.

Have added a screenshot below where the first two logs come from the webpack setup and the latter from my custom logger built with prettycli. Is there a way we can support this where the timestamp can either be provided (so that the timestamp remains on the logs if stored) or else can be generated by this lib by default.

image

@siddharthkp
Copy link
Owner

prettycli isn't smart enough to match loading and successful messages right now 😛

I'm happy to accept a PR that adds support

@subodhpareek18
Copy link
Author

subodhpareek18 commented Jan 20, 2018

Sorry, didn't understand the loading and successful message bit.

I'm just talking about console.log with some data on the RHS (not sure how that is to be done). I'd be happy to make a PR but I do not know how to achieve this placement of text on RHS of the console.

@siddharthkp
Copy link
Owner

siddharthkp commented Jan 20, 2018

I'd suggest reading the source of friendly-errors-webpack-plugin to find out how do they do it (I'm assuming that's where you saw this feature)

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

2 participants