`upg explain` leads to DeprecationWarning on Windows
cpopell opened this issue · comments
ran 'upg explain', got the following error:
(node:39688) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)```
v18.12.1
Can you run upg update
? I can't repro on latest.
I ran it ~3 minutes ago. Do you have a way to show upg ver?
Ohhhhh, the command upg explain
, rather than the Explain command in the loop. I see it now.
That's basically a tradeoff of a library we use for that pasteable editor view. The standard readlines
library won't let us paste a string containing \n
, it submits immediately. I'll have to rewrite the editor view library basically.
For now use upg load [file]
> Explain. No warning.
Will try - btw, I'm not even getting to pasting code. Running upg explain -immediately- causes that problem.
I know. It's the library that opens that nano-like editor up, it uses a raw Buffer()
call which Node warns against now. I'll have to rewrite that entire thing from scratch to fix that.
Just checking: with recent updates, is it still a problem?