You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2019. It is now read-only.
Apologies if this was already discussed, but I couldn't find anything in open/closed issues.
Webpack (since v4?) now uses webpack-log for all of its logging, and I noticed see other projects like webpack-dev-server started to use it too.
In the case of awesome-typescript-loader, I think it would go from something like this (screenshot version):
or (text version):
ℹ 「wds」: Project is running at http://localhost:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: 404s will fallback to /index.html
[at-loader] Using typescript@2.8.1 from typescript and "tsconfig.json" from ...
[at-loader] Checking started in a separate process...
[at-loader] Ok, 0.928 sec.
ℹ 「wdm」: Hash: 683e316aeda30f9f63b7
...
into something like this:
ℹ 「wds」: Project is running at http://localhost:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: 404s will fallback to /index.html
ℹ 「atl」: Using typescript@2.8.1 from typescript and "tsconfig.json" from ...
ℹ 「atl」: Checking started in a separate process...
ℹ 「atl」: Ok, 0.928 sec.
ℹ 「wdm」: Hash: 683e316aeda30f9f63b7
...
Thoughts?
The text was updated successfully, but these errors were encountered:
Apologies if this was already discussed, but I couldn't find anything in open/closed issues.
Webpack (since v4?) now uses webpack-log for all of its logging, and I noticed see other projects like webpack-dev-server started to use it too.
In the case of
awesome-typescript-loader
, I think it would go from something like this (screenshot version):or (text version):
into something like this:
Thoughts?
The text was updated successfully, but these errors were encountered: