isaacscript-lint 1.0.157 → 1.0.160

package/README.md

@@ -26,17 +26,17 @@ Use the `isaacscript init` tool to automatically set up a new mod that has `isaa
 
 ## Why Code Formatting is Important
 
-In the 90's, the most popular scripting language in the world was [Perl](https://www.perl.org/), invented by [Larry Wall](https://en.wikipedia.org/wiki/Larry_Wall). One of Larry's slogans was that "There Is Always More Than One Way To Do It", abbreviated as the TIAMTOWTDI principle. In Perl, there were many different ways to do even the most basic thing, like adding an element to an array. This resulted in a Perl ecosystem where programs often looked nothing like each other, where everyone had different coding styles, and where everything was hard to read and comprehend.
+In the 90's, the most popular scripting language in the world was [Perl](https://www.perl.org/), invented by [Larry Wall](https://en.wikipedia.org/wiki/Larry_Wall). One of Larry's slogans was that "There Is Always More Than One Way To Do It", abbreviated as the TIAMTOWTDI principle. In Perl, there were many different ways to do even the most basic thing, like adding an element to an array. This resulted in a Perl ecosystem where programs often looked nothing like each other, where everyone had different coding styles, and where everything was hard to read and comprehend. <!-- cspell:ignore TIAMTOWTDI -->
 
-One of the key insights of [Guido van Rossum](https://en.wikipedia.org/wiki/Guido_van_Rossum), the creator of the [Python](https://www.python.org/) programming language, was that [code is read much more often than it is written](https://www.python.org/dev/peps/pep-0008/). Python was designed to be concise, clean, and readable. It had standard ways of doing things and recommended that everyone follow the [PEP-8 coding standard](https://www.python.org/dev/peps/pep-0008/). And so, in the 90s, there was a massive movement away from Perl and towards Python. Now, Python is the [most popular programming language in the world](https://pypl.github.io/PYPL.html).
+One of the key insights of [Guido van Rossum](https://en.wikipedia.org/wiki/Guido_van_Rossum), the creator of the [Python](https://www.python.org/) programming language, was that [code is read much more often than it is written](https://www.python.org/dev/peps/pep-0008/). Python was designed to be concise, clean, and readable. It had standard ways of doing things and recommended that everyone follow the [PEP-8 coding standard](https://www.python.org/dev/peps/pep-0008/). And so, in the 90s, there was a massive movement away from Perl and towards Python. Now, Python is the [most popular programming language in the world](https://pypl.github.io/PYPL.html). <!-- cspell:ignore Rossum -->
 
-[Go](https://golang.org/), the programming language designed at Google in 2009, took this concept a step further. They included a code formatter inside of the language itself, called `gofmt` (which is short for "Go formatter"). When you are coding a Go program, it will automatically format all of the code as soon as you save the file. This can be surprising and disturbing for newcomers: "Why does `gofmt` make my code ugly?!"
+[Go](https://golang.org/), the programming language designed at Google in 2009, took this concept a step further. They included a code formatter inside of the language itself, called `gofmt` (which is short for "Go formatter"). When you are coding a Go program, it will automatically format all of the code as soon as you save the file. This can be surprising and disturbing for newcomers: "Why does `gofmt` make my code ugly?!" <!-- cspell:ignore gofmt -->
 
 However, once people get used to the formatter, they realize that it saves them a _tremendous amount of time_. By ignoring all formatting and typing out code "raw", and then summoning the formatter to instantly fix everything, you can quite literally code twice as fast. Rob Pike, one of the creators of Go, famously said that "gofmt's style is no one's favorite, yet gofmt is everyone's favorite". ([This YouTube clip](https://www.youtube.com/embed/PAAkCSZUG1c?start=523&end=568) of Rob is a much-watch!)
 
 `gofmt` is nice because it saves people from mundane code formatting. But there is also a benefit that is entirely separate and not readily apparent. When looking at other people's Go code on StackOverflow or GitHub, you realize that it looks exactly like your code. It's easy to read and comprehend. And you can copy-paste code snippets from other programs into your own applications without having to change anything! For programmers, this is not the norm, and it feels great - it's the hidden superpower of Go.
 
-When Rob says that everyone loves `gofmt`, he isn't lying. Programmers across the world have taken this concept and ran with it. People now use [rustfmt](https://github.com/rust-lang/rustfmt) in [Rust](https://www.rust-lang.org/), [Black](https://github.com/psf/black) in [Python](https://www.python.org/), and [Prettier](https://prettier.io/) in [JavaScript](https://www.javascript.com/) & [TypeScript](https://www.typescriptlang.org/).
+When Rob says that everyone loves `gofmt`, he isn't lying. Programmers across the world have taken this concept and ran with it. People now use [rustfmt](https://github.com/rust-lang/rustfmt) in [Rust](https://www.rust-lang.org/), [Black](https://github.com/psf/black) in [Python](https://www.python.org/), and [Prettier](https://prettier.io/) in [JavaScript](https://www.javascript.com/) & [TypeScript](https://www.typescriptlang.org/). <!-- cspell:ignore rustfmt -->
 
 The root of the problem here is that when people try out a new programming language, they often use the same formatting and conventions that they used in their previous language. This fractures the ecosystem and makes everyone's code inconsistent and hard to read. The lesson of Go is that whenever you code in a new language, you should use the standard style that everyone else uses for that language. In this way, every language can have the superpower that Go has.
 
@@ -105,19 +105,20 @@ module.exports = {
 
 Create a `tsconfig.eslint.json` file in the root of your repository:
 
+<!-- cspell:ignore Gruntfile -->
+
 ```jsonc
-// A special TypeScript configuration file, used by ESLint only
+// A special TypeScript configuration file, used by ESLint only.
 {
   "extends": "./tsconfig.json",
 
-  // A list of the TypeScript files to compile
+  // A list of the TypeScript files to compile:
   "include": [
-    // This must match the "include" setting in the main "tsconfig.json" file
+    // This must match the "include" setting in the main "tsconfig.json" file.
     "./src/**/*.ts",
 
-    // These are ESLint-only inclusions
-    // Usually, this includes any files that are outside of your "src" directory,
-    // such as "webpack.config.js", "jest.config.js", "Gruntfile.js", and so forth
+    // These are ESLint-only inclusions. Usually, this includes any files that are outside of your
+    // "src" directory, such as "webpack.config.js", "jest.config.js", "Gruntfile.js", and so forth.
     "./.eslintrc.js"
   ]
 }

package/package.json

@@ -1,19 +1,19 @@
 {
   "name": "isaacscript-lint",
-  "version": "1.0.157",
-  "description": "An updatable linting dependency container for IsaacScript and TypeScript projects",
+  "version": "1.0.160",
+  "description": "A linting dependency meta-package for IsaacScript and TypeScript projects.",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/IsaacScript/isaacscript-lint.git"
   },
   "license": "MIT",
   "author": "Zamiell",
-  "files": [],
+  "type": "commonjs",
   "dependencies": {
     "@prettier/plugin-xml": "^2.2.0",
     "@typescript-eslint/eslint-plugin": "^5.25.0",
     "@typescript-eslint/parser": "^5.25.0",
-    "cspell": "^5.21.0",
+    "cspell": "^5.21.1",
     "eslint": "^8.15.0",
     "eslint-config-airbnb-base": "^15.0.0",
     "eslint-config-airbnb-typescript": "^17.0.0",
@@ -21,18 +21,14 @@
     "eslint-config-prettier": "^8.5.0",
     "eslint-plugin-eslint-comments": "^3.2.0",
     "eslint-plugin-import": "^2.26.0",
-    "eslint-plugin-isaacscript": "^1.0.43",
+    "eslint-plugin-isaacscript": "^1.0.45",
     "eslint-plugin-jsdoc": "^39.3.0",
-    "eslint-plugin-no-implicit-map-set-loops": "^1.0.3",
     "eslint-plugin-only-warn": "^1.0.3",
     "eslint-plugin-sort-exports": "^0.6.0",
     "prettier": "^2.6.2",
     "prettier-plugin-organize-imports": "^2.3.4",
     "ts-prune": "^0.10.3"
   },
-  "devDependencies": {
-    "npm-check-updates": "^13.0.1"
-  },
   "peerDependencies": {
     "typescript": "^4.6.2"
   }