Skip to content

tailwindcss watcher : abusive console logging #128

@grempe

Description

@grempe

I'd like to ask to look again at addressing the original issue found here

(now closed by its creator, after a comment from @josevalim)

#121

I just spent two frustrating hours tracking down the source of this obscure and very annoying logging message that gets dumped every second in the iex -S mix phx.server console. It has an actual impact on being able to use the console interactively as messages are constantly logging. It was unable to find the source of this message with any kind of search in my codebase or dependencies with a search for 'Done in'. This made it very difficult to track down this issue to its source(s).

My console looks like this... all the time...

...
Done in 487µs
Done in 1ms
Done in 401µs
Done in 1ms
Done in 363µs
Done in 911µs
Done in 403µs
Done in 1ms
Done in 786µs
Done in 1ms
Done in 338µs
Done in 983µs
Done in 272µs
...

The root source of this seems to be:

https://github.com/tailwindlabs/tailwindcss/blob/ca7caae502391fd1360ddd020f3cd80db64081ed/packages/%40tailwindcss-cli/src/commands/build/index.ts#L357

In light of the questionable upstream decision to implement things this way, and since they closed the feature request to look at it long ago, I think it is incumbent on this Phoenix project to provide a mechanism to redirect all STDERR from this external process to /dev/null or an equivalent mechanism to silence this in the name of developer ergonomics.

Please reconsider addressing this in some way.

cc: @aidalgol

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions