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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify "No errors found." message #808

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

cben
Copy link

@cben cben commented Apr 16, 2023

A really minor usability tweak, subjective, up to you if you like it.

In the context of webpack-dev-server, there are 2 async build processes, which may report success/failure:

  • webpack bundle:
    • webpack 5.72.0 compiled with 2 errors in 5492 ms,
    • webpack 5.72.0 compiled successfully in 55345 ms are self-explaining.

There is sometimes a cyan "Type-checking in progress..." between them, but not always.

  • TypeScript checking, which may arrive later:
    • when typescript fails, it starts with non-specific red "ERROR in ./src/..." but next line start with TS error code e.g. TS6133: , so clear enough.
    • when typescript succeeds, the green "No errors found." message may arrive later, and doesn't explain it's specifically what kind of errors. 馃憟

This PR tweaks the last case to say "No typescript errors found." for clarity.

Screenshot from 2023-10-29 15-42-45

@piotr-oles
Copy link
Collaborator

Maybe it would make more sense to just say "No typescript errors found."?

@cben cben changed the title Prepend "TS: " to "No errors found." message Clarify "No errors found." message Oct 29, 2023
@cben
Copy link
Author

cben commented Oct 29, 2023

Maybe it would make more sense to just say "No typescript errors found."?

Done, PTAL.

UPDATE: now also updated waitForNoErrors test helper. needs approval to re-run CI?

When this message appears in context of webpack-dev-server,
it could be unclear what kind of errors (webpack build vs. typescript).
Sometimes there is a prior "Error checking in progress" message,
but not always, and may be far above the "No errors found."
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

Successfully merging this pull request may close these issues.

None yet

2 participants