question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error update plugins (Deprecation warning)

See original GitHub issue
  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate
  • OS version and name: Mojave 10.14.4
  • Hyper.app version: Just installed
  • Node version: 12.4.0
  • Npm version: 6.9.0
  • Yarn version: 1.16.0

Issue

Everytime i launch the terminal I get a message Deprecationwarning Buffer() is deprecated due to security and usability issue

I look for Error update plugins in the issues but didn’t find one about the deprecation warning message.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:25
  • Comments:12

github_iconTop GitHub Comments

5reactions
drdogbot7commented, Apr 7, 2020

For me this was an issue with Yarn trying to use a proxy for some reason (https://github.com/yarnpkg/yarn/issues/4890). I don’t use yarn so I didn’t know it wasn’t working. You can try running the ‘yarn’ command manually in your ‘.hyper_plugins’ folder to see if that’s the issue. Yarn gave me more helpful error messages than Hyper did.

e.g.

cd ~/.hyper_plugins
yarn

You can see if yarn has a proxy set by running:

yarn config list

These commands eventually fixed it for me:

yarn config delete https-proxy
yarn config delete proxy
yarn config set no-proxy true
3reactions
caelinsutchcommented, Aug 11, 2020

@drdogbot7’s suggestion worked for me, but I had to install yarn from brew. For some reason, installing it with npm: npm i -g yarn didn’t work 😦 Either way, glad I figured it out and thanks to everyone from this thread!

Commands that worked for me:

brew install yarn
cd ~/.hyper_plugins
yarn
yarn config delete https-proxy
yarn config delete proxy
yarn config set no-proxy true
Read more comments on GitHub >

github_iconTop Results From Across the Web

Resolving deprecation notices - Shifter Documentation
Most common fix: Update Themes and Plugins. The number one cause of these warnings or errors is an outdated plugin. Updating all of...
Read more >
Deprecated warning | WordPress.org
This kind of issue only occurs when we use the older version of any themes and plugins in our dashboard so make sure...
Read more >
How to stop WordPress from logging deprecation warning ...
Be mindful that it is always better to fix any code resulting in a warning or updating and outdated plugins that may be...
Read more >
WordPress Troubleshooting and How to Fix Common Errors
Plugin Errors. Most errors are caused by plugin updates. So, the first step toward identifying whether a plugin is at fault is to...
Read more >
Fix Your Craft CMS Deprecation Errors - CraftQuest
The first method is to use the Deprecation Warnings utlitiy in the Craft control panel. This gives you a historical view of all...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found