Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature Request: Isomorphic logging (browser support)
See original GitHub issueDescription / Use Case for a Feature
As I’ve said before, I’m really loving tslog in Blitz apps! But there’s one thing I really wish tslog supported, and that is logging in the browser.
Currently I have to be constantly making a cognitive choice between using tslog or console.log based on if I’m in a server or browser context. And this is often since Blitz is a fullstack monolith.
Possible implementation
Provide a separate browser bundle (via package.json browser field) that has a minimal logger without any node.js dependencies. Should be a small as possible for bundle size concerns. Ideally it would accept all the same options, but some of the options would be no-op in the browser.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you very much. It is on my mind for quite some time and you make quite a good suggestion. That is definitely something I would like to add to a 4.0 release. The problem I’ve been stumbling on is how to provide the same API and access all the meta-information without having V8 in place. That would basically mean, either leaving them
undefined, or using some weird hacks like throwing an error and evaluating the string that came out of it.I’d personally be fine to have minimal features in the browser (
undefined)