Bump lodash and @graphql-codegen/cli

[dependabot[bot]]

Bumps lodash to 4.17.21 and updates ancestor dependency @graphql-codegen/cli. These dependencies need to be updated together.

Updates lodash from 4.17.15 to 4.17.21

Commits

• f299b52 Bump to v4.17.21
• c4847eb Improve performance of toNumber, trim and trimEnd on large input strings
• 3469357 Prevent command injection through _.template's variable option
• ded9bc6 Bump to v4.17.20.
• 63150ef Documentation fixes.
• 00f0f62 test.js: Remove trailing comma.
• 846e434 Temporarily use a custom fork of lodash-cli.
• 5d046f3 Re-enable Travis tests on 4.17 branch.
• aa816b3 Remove /npm-package.
• d7fbc52 Bump to v4.17.19
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by bnjmnt4n, a new releaser for lodash since your current version.

Updates @graphql-codegen/cli from 1.5.0 to 1.21.8

Changelog

Sourced from @​graphql-codegen/cli's changelog.

1.21.8

Patch Changes

• e1643e6d4: Fix exception loader.loaderId is not a function caused by conflict with an internal dependency of Codegen.

1.21.7

Patch Changes

• 470336a1: don't require plugins for for config if preset provides plugin. Instead the preset should throw if no plugins were provided.
• Updated dependencies [470336a1]
  • @​graphql-codegen/plugin-helpers@​1.18.8

1.21.6

Patch Changes

• 3b82d1bd: update chokidar

1.21.5

Patch Changes

• dfd25caf: chore(deps): bump graphql-tools versions
• Updated dependencies [dfd25caf]
  • @​graphql-codegen/core@​1.17.10
  • @​graphql-codegen/plugin-helpers@​1.18.7

1.21.4

Patch Changes

• d9212aa0: fix(visitor-plugin-common): guard for a runtime type error
• Updated dependencies [d9212aa0]
  • @​graphql-codegen/plugin-helpers@​1.18.5

1.21.3

Patch Changes

• 23862e7e: fix(naming-convention): revert and pin change-case-all dependency for workaround #3256
• Updated dependencies [23862e7e]
  • @​graphql-codegen/plugin-helpers@​1.18.4

1.21.2

Patch Changes

• 29b75b1e: enhance(namingConvention): use change-case-all instead of individual packages for naming convention

... (truncated)

Commits

• f0f1dad Upcoming Release Changes (#6313)
• e1643e6 Fix for loaders issues with new GraphQL-Tools version (#6375)
• cf7a9df Upcoming Release Changes (#6236)
• 470336a fix: make plugins optional for preset (#6305)
• 495353d chore(deps): update dependency @​types/minimatch to v3.0.5 (#6259)
• 8954a43 chore(deps): update dependency @​types/mkdirp to v1.0.2 (#6260)
• 86aef78 chore(deps): update dependency @​types/listr to v0.14.4 (#6256)
• 988b8b6 chore(deps): update dependency @​types/js-yaml to v4.0.2 (#6255)
• a0ab8c5 chore(deps): update dependency @​types/is-glob to v4.0.2 (#6253)
• 43b686c chore(deps): update dependency @​types/inquirer to v7.3.3 (#6252)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/planetarium/libplanet-explorer-frontend/network/alerts).

[cloudflare-pages[bot]]

Deploying with    Cloudflare Pages

Latest commit:	aedb739
Status:	🚫  Build failed.

View logs

[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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.