build(deps): bump dset from 3.1.2 to 3.1.4 in /pages in the npm_and_yarn group

[dependabot]

Bumps the npm_and_yarn group in /pages with 1 update: dset.

Updates dset from 3.1.2 to 3.1.4

Release notes

Sourced from dset's releases.

v3.1.3

Patches

• Add "types" export conditions for TypeScript "nodenext"/"node16" resolution: #40 Thank you @​Akkuma

---

Full Changelog: lukeed/dset@v3.1.2...v3.1.3

Commits

• 05b1ec0 3.1.4
• 16d6154 fix: prevent proto assignment via implicit string
• 48f14a1 3.1.3
• aca90fb chore: add "types" conditions for TS "nodenext" resolution (#40)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Here are some friendly prose warnings from write-good:

In ./CODE_OF_CONDUCT.md
=============
- Giving and gracefully accepting constructive feedback
             ^^^^^^^^^^
"gracefully" can weaken meaning on line 21 at column 13
-------------
sing on what is best not just for us as individuals, but for the overall communi
                         ^^^^
"just" can weaken meaning on line 24 at column 31
-------------
individuals, but for the overall community
                         ^^^^^^^
"overall" is wordy or unneeded on line 24 at column 71
-------------
t which could reasonably be considered inappropriate in a professional
                         ^^^^^^^^^^^^^
"be considered" may be passive voice on line 34 at column 39
-------------
nacceptable behavior may be reported to
                         ^^^^^^^^^^^
"be reported" may be passive voice on line 57 at column 72
-------------
complaints will be reviewed and investigated promptly and fairly.
                ^^^^^^^^^^^
"be reviewed" may be passive voice on line 59 at column 16
-------------
eviewed and investigated promptly and fairly.
                         ^^^^^^^^
"promptly" can weaken meaning on line 59 at column 45
-------------
nvestigated promptly and fairly.
                         ^^^^^^
"fairly" is a weasel word and can weaken meaning on line 59 at column 58
-------------
All community leaders are obligated to respect the privacy and security of the r
                      ^^^^^^^^^^^^^
"are obligated" may be passive voice on line 61 at column 22
-------------
te. A public apology may be requested.
                         ^^^^^^^^^^^^
"be requested" may be passive voice on line 76 at column 36
-------------
Conduct, is allowed during this period. Violating these terms may lead to a perm
         ^^^^^^^^^^
"is allowed" may be passive voice on line 96 at column 9
-------------
This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi
                     ^^^^^^^^^^
"is adapted" may be passive voice on line 110 at column 21
-------------
munity Impact Guidelines were inspired by [Mozilla's code of conduct enforcement
                         ^^^^^^^^^^^^^
"were inspired" may be passive voice on line 114 at column 28


In ./src/AnniversaryReminder/wwwroot/lib/jquery-validation/LICENSE.md
=============
the rights to use, copy, modify,
                         ^^^^^^
"modify" is wordy or unneeded on line 7 at column 75
-------------
ons to whom the Software is furnished to do so, subject to the following
                         ^^^^^^^^^^^^
"is furnished" may be passive voice on line 9 at column 36
-------------
d this permission notice shall be included in all copies or
                         ^^^^^
"shall" is wordy or unneeded on line 12 at column 54
-------------
 permission notice shall be included in all copies or
                         ^^^^^^^^^^^
"be included" may be passive voice on line 12 at column 60
-------------
substantial portions of the Software.
^^^^^^^^^^^
"substantial" is wordy or unneeded on line 13 at column 0
-------------
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
             ^^^^^^^^^^^
"IS PROVIDED" may be passive voice on line 15 at column 13
-------------
NFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
                         ^^^^^
"SHALL" is wordy or unneeded on line 17 at column 41


In ./README.md
=============
anniversaryreminder is a program that do you remind you to anniversaries in a co
^^^^^^^^^^^^^^^^^^^
"anniversaryreminder" is repeated on line 3 at column 0
-------------
n redistribute it and/or modify it under the
                         ^^^^^^
"modify" is wordy or unneeded on line 29 at column 69
-------------
additional information.
^^^^^^^^^^
"additional" is wordy or unneeded on line 34 at column 0


In ./.github/PULL_REQUEST_TEMPLATE.md
=============
s one or more issues, or is related to another PR, link to them here. -->
                         ^^^^^^^^^^
"is related" may be passive voice on line 10 at column 55
-------------
## How Has This Been Tested?
                ^^^^^^^^^^^
"Been Tested" may be passive voice on line 17 at column 16
-------------
request before all these are done, but they should be done before getting merged
                         ^^^^^^^^
"are done" may be passive voice on line 26 at column 51
-------------
re done, but they should be done before getting merged. -->
                         ^^^^^^^
"be done" may be passive voice on line 26 at column 77
-------------
hanges are notable, they are documented in
                         ^^^^^^^^^^^^^^
"are documented" may be passive voice on line 40 at column 41


In ./.github/ISSUE_TEMPLATE/bug_report.md
=============
<!-- Your environment is usually important for finding the cause of the bug. -->
                         ^^^^^^^
"usually" can weaken meaning on line 29 at column 25
-------------
**Additional context**
  ^^^^^^^^^^
"Additional" is wordy or unneeded on line 35 at column 2


In ./.github/ISSUE_TEMPLATE/feature_request.md
=============
**Additional context**
  ^^^^^^^^^^
"Additional" is wordy or unneeded on line 21 at column 2


In ./pages/README.md
=============
s/' directory. Each page is
                         ^^^^^^^^^^
"is
exposed" may be passive voice on line 32 at column 81
-------------
assets, like images, can be placed in the 'public/' directory.
                         ^^^^^^^^^
"be placed" may be passive voice on line 38 at column 36
-------------
All commands are run from the root of the project, from a terminal:
             ^^^^^^^
"are run" may be passive voice on line 42 at column 13


In ./CHANGELOG.md
=============
- Appveyor Build is failed
                 ^^^^^^^^^
"is failed" may be passive voice on line 9 at column 17


In ./SECURITY.md
=============
ions of your project are currently being
                         ^^^^^^^^^
"currently" can weaken meaning on line 5 at column 73
-------------
ur project are currently being
                         ^^^^^^^^^^^^^^^
"being
supported" may be passive voice on line 5 at column 83
-------------
ect if the vulnerability is accepted or declined, etc.
                         ^^^^^^^^^^^
"is accepted" may be passive voice on line 20 at column 51


In ./CONTRIBUTING.md
=============
Submit only relevant commits. We don't mind many commits in a pull request, but 
       ^^^^
"only" can weaken meaning on line 10 at column 7
-------------
t commits. We don't mind many commits in a pull request, but they
                         ^^^^
"many" is a weasel word and can weaken meaning on line 10 at column 44
-------------
 The pull request should be created from a feature branch, and
                         ^^^^^^^^^^
"be created" may be passive voice on line 13 at column 51
-------------
commits that changes too many things at the
                         ^^^^
"many" can weaken meaning on line 32 at column 68
-------------
ts that changes too many things at the
                         ^^^^^^
"things" can weaken meaning on line 32 at column 73
-------------
  same time are very hard to review. Split large commits into smaller. See this
                ^^^^
"very" is a weasel word and can weaken meaning on line 33 at column 16
-------------
  be run using the command
  ^^^^^^
"be run" may be passive voice on line 37 at column 2
-------------
Especially if you modify something existing, be very clear! Have you changed any
^^^^^^^^^^
"Especially" can weaken meaning on line 49 at column 0
-------------
Especially if you modify something existing, be very clear! Have you changed any
                  ^^^^^^
"modify" is wordy or unneeded on line 49 at column 18
-------------
y something existing, be very clear! Have you changed any
                         ^^^^
"very" is a weasel word and can weaken meaning on line 49 at column 48
-------------
algorithms, or did you just intend to reorder the code? Justify why the changes 
                       ^^^^
"just" can weaken meaning on line 50 at column 23
-------------
 Justify why the changes are
                         ^^^^^^^^^^
"are
needed" may be passive voice on line 50 at column 80
-------------
are things we want help with.
    ^^^^^^
"things" can weaken meaning on line 84 at column 4
-------------
git merge --ff-only upstream/dev
               ^^^^
"only" can weaken meaning on line 104 at column 15
-------------
  and that it's created off of _dev_. Tip: Give it a descriptive name and includ
                        ^^^^^^
"off of" is wordy or unneeded on line 111 at column 24
-------------
  issue number, e.g. 'implement-lengthframeencoder-323' or '295-implement-recvbu
                      ^^^^^^^^^
"implement" is wordy or unneeded on line 112 at column 22
-------------
  so that others can see what is being worked on.
 ^^
" s" adds no meaning on line 113 at column 1
-------------
t others can see what is being worked on.
                         ^^^^^^^^^^^^
"being worked" may be passive voice on line 113 at column 33
-------------
away in your branch it's quite possible that your upstream _dev_
                         ^^^^^
"quite" is a weasel word on line 136 at column 46
-------------
may be updated. If this happens you should:
    ^^^^^^^^^^
"be updated" may be passive voice on line 137 at column 4
-------------
git merge --ff-only upstream/dev
               ^^^^
"only" can weaken meaning on line 151 at column 15
-------------
 to do this ends up with several
                         ^^^^^^^
"several" is a weasel word on line 165 at column 77
-------------
 you may want to do this quite often,
                         ^^^^^
"quite" is a weasel word on line 170 at column 73
-------------
bmitting a Pull request, just commit to
                         ^^^^
"just" can weaken meaning on line 175 at column 72
-------------
anch and push the branch just like you did the first time. This commit will
                         ^^^^
"just" can weaken meaning on line 176 at column 38
-------------
automatically be included in the Pull request. If we ask you to change already p
              ^^^^^^^^^^^
"be included" may be passive voice on line 177 at column 14
-------------
 can create a new branch off of _develop_ and then cherry pick the commits
                         ^^^^^^
"off of" is wordy or unneeded on line 199 at column 31