Devon Carew

Hi; thanks for the contribution and the interest. Unfortunately, this repository was not being actively maintained and as per the [readme](https://github.com/dart-lang/js_facade_gen), we've made the decision to archive it. We'll continue...

Hi - thanks for the inquiry. This repository was not being actively maintained and after consideration - as per the [readme](https://github.com/dart-lang/js_facade_gen) - we've made the decision to archive it. We'll...

Hi - thanks for the inquiry. This repository was not being actively maintained and after consideration - as per the [readme](https://github.com/dart-lang/js_facade_gen) - we've made the decision to archive it. We'll...

Hi - thanks for the inquiry. This repository was not being actively maintained and after consideration - as per the [readme](https://github.com/dart-lang/js_facade_gen) - we've made the decision to archive it. We'll...

I think it's mostly taste; I normally log at the `info` level. The more verbose levels are likely only used in more specific circumstances. I'll keep this issue open as...

@AmanNegi - thanks for the contribution! We generally have to be conservative with API additions to this package - it's widely used in the ecosystem and implemented in a few...

Hmm, yes, this is a core package, and I'd be concerned that `developer.log()` is not zero cost (esp. when there's a debugging client hooked up). I'm curious - what options...

I'm very much in favor of making structured logging visible to developers and improving the support for logging in our libraries and developer tools. I think this meeds a bit...

I'm not sure how compatible the change would be from defining levels as a psuedo-enum class to using actual enums (i.e., would existing clients see errors)? I agree the change...

> What do you think? Would you welcome a PR with these changes? I could prepare something. We've held off on the screaming caps change just because this package is...