Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: moxystudio/node-cross-spawn
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v6.0.4
Choose a base ref
...
head repository: moxystudio/node-cross-spawn
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v6.0.5
Choose a head ref
  • 7 commits
  • 6 files changed
  • 3 contributors

Commits on Feb 5, 2018

  1. Configuration menu
    Copy the full SHA
    35b1ff0 View commit details
    Browse the repository at this point in the history
  2. Merge pull request #92 from moxystudio/greenkeeper/eslint-config-moxy…

    …-5.0.0
    
    Update eslint-config-moxy to the latest version 🚀
    satazor authored Feb 5, 2018
    Configuration menu
    Copy the full SHA
    213aa43 View commit details
    Browse the repository at this point in the history

Commits on Feb 23, 2018

  1. Configuration menu
    Copy the full SHA
    39166eb View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    6b64987 View commit details
    Browse the repository at this point in the history

Commits on Mar 2, 2018

  1. fix: avoid using deprecated Buffer constructor (#94)

    * fix: avoid using deprecated Buffer constructor
    
    Buffer.alloc() is supported on Node.js >= 4.5.0, and allocates a zero-filled
    buffer on all supported versions.
    
    This solves two issues:
     * Buffer() constructor (aka 'new Buffer()') is deprecated, so avoid using it
     * On 4.x and 6.x, Buffer(number) is not zero-filled, so this code was
       allocating an uninitialized Buffer when file length was less than 150, so
       the behaviour of readShebang() was actually undefined in that case (as in
       could have returned anything, depending on the uninitialized memory chunk).
    
    Refs: https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor
    
    * readShebang: name reused inline constant
    
    '150' was used two times, it deserves a name.
    It's the size of the pre-read buffer.
    
    * readShebang: Buffer API compat for old Node.js
    
    To be reverted when dropping outdated Node.js versions support.
    ChALkeR authored and satazor committed Mar 2, 2018
    Configuration menu
    Copy the full SHA
    d5770df View commit details
    Browse the repository at this point in the history
  2. chore: fix linting errors

    satazor committed Mar 2, 2018
    Configuration menu
    Copy the full SHA
    ae85d40 View commit details
    Browse the repository at this point in the history
  3. chore(release): 6.0.5

    satazor committed Mar 2, 2018
    Configuration menu
    Copy the full SHA
    301187a View commit details
    Browse the repository at this point in the history
Loading