[Snyk] Upgrade load-grunt-tasks from 3.5.2 to 5.1.0

[AdamOswald]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade load-grunt-tasks from 3.5.2 to 5.1.0.

 :information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

*Warning:* This is a major version upgrade, and may be a breaking change. - The recommended version is **3 versions** ahead of your current version. - The recommended version was released **3 years ago**, on 2019-07-31.

Release notes

Package name: load-grunt-tasks

• 5.1.0 - 2019-07-31
  
  • Print a useful error if package.json is missing (#61) 6234bc9

  v5.0.0...v5.1.0

• 5.0.0 - 2019-05-23
  

  Breaking:

  • Require Node.js 8 a928bc7

  Enhancements:

  • Upgrade dependencies a928bc7

  v4.0.0...v5.0.0

    </li>
    <li>
      <b>4.0.0</b> - <a href="https://snyk.io/redirect/github/sindresorhus/load-grunt-tasks/releases/tag/v4.0.0">2018-05-07</a></br><p>4.0.0</p>
    </li>
    <li>
      <b>3.5.2</b> - <a href="https://snyk.io/redirect/github/sindresorhus/load-grunt-tasks/releases/tag/v3.5.2">2016-08-12</a></br><p>3.5.2</p>
    </li>
  </ul>
  from <a href="https://snyk.io/redirect/github/sindresorhus/load-grunt-tasks/releases">load-grunt-tasks GitHub release notes</a>

Commit messages

Package name: load-grunt-tasks

• fddcf81 5.1.0
• 6234bc9 Print a useful error if package.json is missing (#61)
• 919a1d6 5.0.0
• a928bc7 Require Node.js 8 and upgrade dependencies
• 81c6b67 Enable the repo sponsor button
• 73a8298 4.0.0
• 470335a Resolve packages relative to the package.json file instead of to the root
• e6797ad Require Node.js 6 and bump dependencies

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[difflens[bot]]

View changes in DiffLens

[guide-bot[bot]]

Thanks for opening this Pull Request! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.

[viezly[bot]]

Changes preview:

Legend:

👀 Review pull request on Viezly

[difflens[bot]]

View changes in DiffLens

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.