csscomb.js icon indicating copy to clipboard operation
csscomb.js copied to clipboard

Node error at first run, and then the action disappears from Control Panel

Open loikein opened this issue 5 years ago • 1 comments

Hi, I have no knowledge of node, but any help is welcome. Tried remove & reinstall, the same thing happens again.

Error message:

CSScomb error:
(node:96684) UnhandledPromiseRejectionWarning: [object Object]
(Use `node --trace-warnings ...` to show where the warning was created)
(node:96684) 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: 2)
(node:96684) [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.

Versions: macOS 10.15.4 (19E287)

$ node --version
# v14.2.0

$ which node
# /usr/local/bin/node

$ subl --version
# Sublime Text Build 3211

loikein avatar May 18 '20 06:05 loikein

I found a bug that would prevent CSScomb: Try online from running, and reinstalled the plugin. The following error message shows:

CSScomb error:
(node:96860) UnhandledPromiseRejectionWarning: [object Object]
(Use `node --trace-warnings ...` to show where the warning was created)
(node:96860) 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: 2)
(node:96860) [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.

loikein avatar May 18 '20 06:05 loikein