style: apply new prettier config to all files

.github/CODE_OF_CONDUCT.md

@@ -2,45 +2,73 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Examples of behavior that contributes to creating a positive environment
+include:
 
--   Using welcoming and inclusive language
--   Being respectful of differing viewpoints and experiences
--   Gracefully accepting constructive criticism
--   Focusing on what is best for the community
--   Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
--   The use of sexualized language or imagery and unwelcome sexual attention or advances
--   Trolling, insulting/derogatory comments, and personal or political attacks
--   Public or private harassment
--   Publishing others' private information, such as a physical or electronic address, without explicit permission
--   Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@favware.tech. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at support@favware.tech. The project
+team will review and investigate all complaints, and will respond in a way that
+it deems appropriate to the circumstances. The project team is obligated to
+maintain confidentiality with regard to the reporter of an incident. Further
+details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
 [version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -10,21 +10,30 @@
 
 ## Contributing to the code
 
-**The issue tracker is only for issue reporting or proposals/suggestions. If you have a question, you can find us in our [Discord Server][discord server]**.
+**The issue tracker is only for issue reporting or proposals/suggestions. If you
+have a question, you can find us in our [Discord Server][discord server]**.
 
-To contribute to this repository, feel free to create a new fork of the repository and
-submit a pull request. We highly suggest [ESLint] to be installed
-in your text editor or IDE of your choice to ensure builds from GitHub Actions do not fail.
+To contribute to this repository, feel free to create a new fork of the
+repository and submit a pull request. We highly suggest [ESLint] to be installed
+in your text editor or IDE of your choice to ensure builds from GitHub Actions
+do not fail.
 
-**_Before committing and pushing your changes, please ensure that you do not have any linting errors by running `yarn lint`!_**
+**_Before committing and pushing your changes, please ensure that you do not
+have any linting errors by running `yarn lint`!_**
 
 ### NPM Deprecate Guidelines
 
-There are a number of guidelines considered when reviewing Pull Requests to be merged. _This is by no means an exhaustive list, but here are some things to consider before/while submitting your ideas._
-
--   Everything in NPM Deprecate should be generally useful for the majority of users. Don't let that stop you if you've got a good concept though, as your idea still might be a great addition.
--   Everything should follow our ESLint rules as closely as possible, and should pass linting even if you must disable a rule for a single line.
--   Scripts that are to be ran outside of the scope of the bot should be added to [scripts] directory and should be in the `.mjs` file format.
+There are a number of guidelines considered when reviewing Pull Requests to be
+merged. _This is by no means an exhaustive list, but here are some things to
+consider before/while submitting your ideas._
+
+- Everything in NPM Deprecate should be generally useful for the majority of
+  users. Don't let that stop you if you've got a good concept though, as your
+  idea still might be a great addition.
+- Everything should follow our ESLint rules as closely as possible, and should
+  pass linting even if you must disable a rule for a single line.
+- Scripts that are to be ran outside of the scope of the bot should be added to
+  [scripts] directory and should be in the `.mjs` file format.
 
 <!-- Link Dump -->
 

.github/ISSUE_TEMPLATE/question---general-support-request.md

@@ -6,10 +6,12 @@ labels: 'Type: Question'
 assignees: 'favna'
 ---
 
-Seriously, we only use this issue tracker for bugs in the library itself and feature requests for it.
-We don't typically answer questions or help with support issues here.
-Instead, please ask in one of the support channels in our Discord server:
+Seriously, we only use this issue tracker for bugs in the library itself and
+feature requests for it. We don't typically answer questions or help with
+support issues here. Instead, please ask in one of the support channels in our
+Discord server:
 
 https://join.favware.tech
 
-Any issues that don't directly involve a bug in the library or a feature request will likely be closed and redirected to the Discord server.
+Any issues that don't directly involve a bug in the library or a feature request
+will likely be closed and redirected to the Discord server.

.github/SECURITY.md

@@ -2,7 +2,9 @@
 
 ## Reporting a Vulnerability
 
-If you find a vulnerability in the npm-deprecate codebase please report it immediately. You can do so through one of the following methods:
+If you find a vulnerability in the npm-deprecate codebase please report it
+immediately. You can do so through one of the following methods:
 
--   Use the GitHub issue tracker to report the issue
--   Join the Discord server through https://join.favware.tech and use the "#support" channel.
+- Use the GitHub issue tracker to report the issue
+- Join the Discord server through https://join.favware.tech and use the
+  "#support" channel.

.github/problemMatchers/eslint.json

@@ -1,22 +1,22 @@
 {
-	"problemMatcher": [
-		{
-			"owner": "eslint-stylish",
-			"pattern": [
-				{
-					"regexp": "^([^\\s].*)$",
-					"file": 1
-				},
-				{
-					"regexp": "^\\s+(\\d+):(\\d+)\\s+(error|warning|info)\\s+(.*)\\s\\s+(.*)$",
-					"line": 1,
-					"column": 2,
-					"severity": 3,
-					"message": 4,
-					"code": 5,
-					"loop": true
-				}
-			]
-		}
-	]
+  "problemMatcher": [
+    {
+      "owner": "eslint-stylish",
+      "pattern": [
+        {
+          "regexp": "^([^\\s].*)$",
+          "file": 1
+        },
+        {
+          "regexp": "^\\s+(\\d+):(\\d+)\\s+(error|warning|info)\\s+(.*)\\s\\s+(.*)$",
+          "line": 1,
+          "column": 2,
+          "severity": 3,
+          "message": 4,
+          "code": 5,
+          "loop": true
+        }
+      ]
+    }
+  ]
 }

.github/problemMatchers/tsc.json

@@ -1,17 +1,17 @@
 {
-	"problemMatcher": [
-		{
-			"owner": "tsc",
-			"pattern": [
-				{
-					"regexp": "^(?:\\s+\\d+\\>)?([^\\s].*)\\((\\d+|\\d+,\\d+|\\d+,\\d+,\\d+,\\d+)\\)\\s*:\\s+(error|warning|info)\\s+(\\w{1,2}\\d+)\\s*:\\s*(.*)$",
-					"file": 1,
-					"location": 2,
-					"severity": 3,
-					"code": 4,
-					"message": 5
-				}
-			]
-		}
-	]
+  "problemMatcher": [
+    {
+      "owner": "tsc",
+      "pattern": [
+        {
+          "regexp": "^(?:\\s+\\d+\\>)?([^\\s].*)\\((\\d+|\\d+,\\d+|\\d+,\\d+,\\d+,\\d+)\\)\\s*:\\s+(error|warning|info)\\s+(\\w{1,2}\\d+)\\s*:\\s*(.*)$",
+          "file": 1,
+          "location": 2,
+          "severity": 3,
+          "code": 4,
+          "message": 5
+        }
+      ]
+    }
+  ]
 }

.github/renovate.json

@@ -1,4 +1,4 @@
 {
-	"$schema": "https://docs.renovatebot.com/renovate-schema.json",
-	"extends": ["github>sapphiredev/readme:sapphire-renovate"]
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": ["github>sapphiredev/readme:sapphire-renovate"]
 }

LICENSE.md

@@ -2,23 +2,19 @@
 
 Copyright © `2021` `Favware`
 
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the “Software”), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the “Software”), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
 
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.