updated dependencies according to npm audit

[bt-nia]

fixes #30 (NOT the Snyk reported issue!)

➜  glob-parent git:(master) ✗ npm test

> glob-parent@5.1.1 pretest /private/tmp/glob-parent
> npm run lint


> glob-parent@5.1.1 lint /private/tmp/glob-parent
> eslint .


> glob-parent@5.1.1 test /private/tmp/glob-parent
> nyc mocha --async-only



  glob-parent
    ✓ should strip glob magic to return parent path
    ✓ should respect escaped characters
    ✓ should respect glob enclosures with embedded separators
    ✓ should handle nested braces
    ✓ should return parent dirname from non-glob paths
    ✓ should respect disabled auto flip backslashes

  glob2base test patterns
    ✓ should get a base name
    ✓ should get a base name from a nested glob
    ✓ should get a base name from a flat file
    ✓ should get a base name from character class pattern
    ✓ should get a base name from brace , expansion
    ✓ should get a base name from brace .. expansion
    ✓ should get a base name from extglob
    ✓ should get a base name from a path with non-exglob parens
    ✓ should get a base name from a complex brace glob


  15 passing (10ms)

----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |   94.44 |    77.78 |     100 |   94.44 |
 index.js |   94.44 |    77.78 |     100 |   94.44 | 23
----------|---------|----------|---------|---------|-------------------

[phated]

In v15, node 8 is required. This package currently supports node 6+; however, the gulp team will be updating the repository template, which drops node support for node <10 and updates nyc to this version.

As this is a devDep, you don't have to worry about this npm audit in your project, as devDeps aren't installed or used in your own deps.

[paulmillr]

@phated maybe drop node <12? node 10 eol is april 2021

[phated]

@paulmillr as I've said before, just because node core EoLs stuff at a ridiculous pace, doesn't mean I plan to leave users high-and-dry like some other prominent maintainers. We will, however, be more brisk in releasing new stuff, now that we have tooling in place to do repo upgrades, etc