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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError when parseErrorMessage #461

Open
wuxianucw opened this issue Jun 23, 2021 · 0 comments
Open

TypeError when parseErrorMessage #461

wuxianucw opened this issue Jun 23, 2021 · 0 comments

Comments

@wuxianucw
Copy link

Just now I'm using UnCSS to process my files, but I got such error below.

(node:896) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'substr' of undefined
    at Object.parseErrorMessage (F:\npm\node_modules\uncss\src\utility.js:171:30)
    at processWithTextApi (F:\npm\node_modules\uncss\src\uncss.js:144:23)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:896) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:896) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I soon found out that this was because one of my files was using an online CSS, while the fetched CSS unexpectedly became a binary file. I guess parseErrorMessage is not processing this condition. So I got the error.

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

No branches or pull requests

1 participant