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
I'm developing a Figma plugin and the code runs on a sandbox with no access to window or process so although I'm using Chrome Dev Tools to see the messages, debug is not coloring them.
Also, I can't set environment variables, so I would like to useColor to true, like I'm using Debugger.enable('cva:*');
The text was updated successfully, but these errors were encountered:
In the mean time, for any Typescript coders, this can force debug to use colors:
// This is necessary because the typings are out of date on Jan 7th, 2023// eslint-disable-next-line @typescript-eslint/no-unsafe-member-access, @typescript-eslint/no-explicit-any(Debuggerasany).useColors=()=>true;
This custom debugger based on debug-js (part of metalsmith.js) demonstrates how you can assign fixed colors per channel (eg :warn, :info etc) & pipe the output to a file (Debugger.handle = fileLogHandler('my.log'))
Hi,
I'm developing a Figma plugin and the code runs on a sandbox with no access to
window
orprocess
so although I'm using Chrome Dev Tools to see the messages,debug
is not coloring them.Also, I can't set environment variables, so I would like to
useColor
totrue
, like I'm usingDebugger.enable('cva:*');
The text was updated successfully, but these errors were encountered: