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:
- Created 4 years ago
- Reactions:25
- Comments:12
Top 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 >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
You can see if yarn has a proxy set by running:
These commands eventually fixed it for me:
@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: