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.

Deprecated Buffer usage in load-bmfont

See original GitHub issue

Expected Behavior

No deprecation warnings are generated by using jimp.

Current Behavior

load-bmfont (at least) uses the Buffer constructor, which is deprecated.

Failure Information (for bugs)

Steps to Reproduce

require("jimp");

Context

I tried resolving this in load-bmfont, but the maintainers are not responding in inquiries.

Jimp Version: 0.5.6
Operating System: Windows
Node version: LTS

Failure Logs

(node:21464) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Issue Analytics

State:
Created 5 years ago
Comments:11

Top GitHub Comments

1reaction

hipstersmoothiecommented, Nov 28, 2018

hmmm okay. i’ll give it a try later. Thanks for the code!

0reactions

oliversalzburgcommented, Apr 20, 2020

Well, my PR in the dependency is still open, but the module seems to be very unmaintained or the maintainer very unreliable. If the funcationality is important, maybe it should be moved into the core and the code could be fixed there.

I personally have no interest in working on that, as we have moved away from jimp, due to this poor example of maintenance. If someone feels the need to work on a fix for this, please open a new issue, so that I don’t get any more notifications about this.

Top Results From Across the Web

Buffer() is deprecated due to security and usability issues ...

The use of the deprecated new Buffer() constructor (i.E. as used by Yarn) can cause deprecation warnings. Therefore one should NOT use the ......

Porting to the Buffer.from() / Buffer.alloc() API - Node.js

This guide explains how to migrate to safe Buffer constructor methods. The migration fixes the following deprecation warning: The Buffer() and new Buffer() ......

Understanding the Buffer Deprecation in Node.js 10

Deprecating the Buffer constructor came back into the conversation recently because improper usage of the Buffer constructor is still a path ...

Buffer() is deprecated due to security and usability issues

Description: I've got a warning for deprecation, please reconsider to change Buffer(). DeprecationWarning: Buffer() is deprecated due to ...

no-buffer-constructor - ESLint - Pluggable JavaScript Linter

This rule was deprecated in ESLint v7.0.0. Please use the corresponding rule in eslint-plugin-node . In Node.js, the behavior of the Buffer constructor...