Skip to content

Commit

Permalink
changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
feross committed Apr 5, 2017
1 parent 9223ed2 commit f107095
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,14 @@ console in recent versions of Node.js. This often confuses users and leads to
unnecessary support tickets for project maintainers.

Some deprecated APIs are even insecure (or at least prone to incorrect usage) which
can have serious security implications. For that reason, `standard` now prevents
usage of `Buffer(num)` or `new Buffer(num)` since these functions return
uninitialized program memory which could contain private user information or
confidential secret keys.
can have serious security implications. For that reason, `standard` now considers
usage of `Buffer(num)` to be an error, since this function returns uninitialized
program memory which could contain confidential information like passwords or keys.

Instead of `Buffer(num)`, consider using `Buffer.alloc(num)` or `Buffer.from(obj)`
which make the programmer intention much clearer. These new functions exist in all
currently supported versions of Node.js, including Node.js 4.x. For more
background, [see this Node.js issue](https://github.com/nodejs/node/issues/4660).
which make the programmer's intent clearer. These functions exist in all currently
supported versions of Node.js, including Node.js 4.x. For more background,
[see this Node.js issue](https://github.com/nodejs/node/issues/4660).

We also improved some rules to support common patterns in code bases that use
React, JSX, and Flow.
Expand Down

0 comments on commit f107095

Please sign in to comment.