Bump why-is-node-running from 2.3.0 to 3.2.0

[dependabot]

Bumps why-is-node-running from 2.3.0 to 3.2.0.

Release notes

Sourced from why-is-node-running's releases.

v3.2.0

Notable Changes

Relative file paths

The file paths shown in the output are now relative to the current working directory, if a path is outside of the current working directory the full absolute path will be used instead.

Before

There are 4 handle(s) keeping the process running
Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)

/path/to/project/example.js:10 - startServer()
TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)

/path/to/project/example.js:10 - startServer()
Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)

/path/to/project/example.js:11 - startServer()
TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)

/path/to/project/example.js:11 - startServer()

After

There are 4 handle(s) keeping the process running
Timeout
example.js:6  - setInterval(() => {}, 1000)

example.js:10 - startServer()
TCPSERVERWRAP
example.js:7  - server.listen(0)

example.js:10 - startServer()
Timeout
example.js:6  - setInterval(() => {}, 1000)

example.js:11 - startServer()
TCPSERVERWRAP
example.js:7  - server.listen(0)

example.js:11 - startServer()

No more dependencies

... (truncated)

Commits

• 37b48fb 3.2.0
• 9f29cb8 Replace stackback with internal implementation (#80)
• bbcf168 Refactor code to modern JavaScript syntax (#79)
• e73f692 Use relative paths for files under current working directory (#78)
• c1962ce Remove dependeny on siginfo package (#77)
• 06ca4c4 Add files field to package.json (#76)
• bbd25d1 Update example code to match README (#75)
• 363837c Re-write README to better present installation options (#74)
• 537868e Add correct Node.js versions to README (#73)
• 4fea0e9 Add missing permissions to publish workflow (#72)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by jkoops, a new releaser for why-is-node-running since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.