isaacscript-lint 1.0.150 → 1.0.153

package/README.md

@@ -1,5 +1,7 @@
 # isaacscript-lint
 
+<!-- markdownlint-disable MD033 -->
+
 [![npm version](https://img.shields.io/npm/v/isaacscript-lint.svg)](https://www.npmjs.com/package/isaacscript-lint)
 
 `isaacscript-lint` is a helper package to install all of the dependencies necessary for ESLint to work with a typical TypeScript project or a typical IsaacScript mod.
@@ -30,7 +32,7 @@ One of the key insights of [Guido van Rossum](https://en.wikipedia.org/wiki/Guid
 
 [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?!"
 
-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!)
+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.
 
@@ -48,7 +50,7 @@ Historically, the the most popular style guide is the world is the [Airbnb JavaS
 
 ESLint is the industry standard tool for linting in JavaScript and TypeScript. Airbnb helpfully provides an ESLint configuration with most of their style recommendations. ESLint can function in a way similar to `gofmt` by configuring your text editor to do `eslint --fix` on save. However, this has a lot of limitations. It can't automatically fix everything and leaves a lot up to the end user to fix.
 
-[Prettier](https://prettier.io/) was released in 2017 and it has quickly become very widespread. (It could *probably* also be considered to be industry standard in 2022.) Prettier works by completely rebuilding your code from scratch using the [AST](https://en.wikipedia.org/wiki/Abstract_syntax_tree), which allows it to make much better transformations than pure ESLint can.
+[Prettier](https://prettier.io/) was released in 2017 and it has quickly become very widespread. (It could _probably_ also be considered to be industry standard in 2022.) Prettier works by completely rebuilding your code from scratch using the [AST](https://en.wikipedia.org/wiki/Abstract_syntax_tree), which allows it to make much better transformations than pure ESLint can.
 
 Because of the advantages of Prettier, we use it on top of the Airbnb config, and prefer Prettier's changes if there are any conflicts. Any ESLint rules that conflict with Prettier are turned off with [`eslint-config-prettier`](https://github.com/prettier/eslint-config-prettier).
 
@@ -116,8 +118,8 @@ Create a `tsconfig.eslint.json` file in the root of your repository:
     // 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",
-  ],
+    "./.eslintrc.js"
+  ]
 }
 ```
 
@@ -157,20 +159,16 @@ Furthermore, you will probably want Prettier and ESLint to be run automatically
 // These are Visual Studio Code settings that should apply to this particular repository
 {
   "[javascript]": {
-    "editor.codeActionsOnSave": [
-      "source.fixAll.eslint",
-    ],
+    "editor.codeActionsOnSave": ["source.fixAll.eslint"],
     "editor.defaultFormatter": "esbenp.prettier-vscode",
-    "editor.formatOnSave": true,
+    "editor.formatOnSave": true
   },
 
   "[typescript]": {
-    "editor.codeActionsOnSave": [
-      "source.fixAll.eslint",
-    ],
+    "editor.codeActionsOnSave": ["source.fixAll.eslint"],
     "editor.defaultFormatter": "esbenp.prettier-vscode",
-    "editor.formatOnSave": true,
-  },
+    "editor.formatOnSave": true
+  }
 }
 ```
 
@@ -190,8 +188,8 @@ Optionally, you can also provide a hint to anyone cloning your repository that t
   "recommendations": [
     "esbenp.prettier-vscode", // The TypeScript formatter
     "dbaeumer.vscode-eslint", // The TypeScript linter
-    "streetsidesoftware.code-spell-checker", // A spell-checker extension based on cspell
-  ],
+    "streetsidesoftware.code-spell-checker" // A spell-checker extension based on cspell
+  ]
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "isaacscript-lint",
-  "version": "1.0.150",
+  "version": "1.0.153",
   "description": "An updatable linting dependency container for IsaacScript and TypeScript projects",
   "repository": {
     "type": "git",
@@ -8,6 +8,7 @@
   },
   "license": "MIT",
   "author": "Zamiell",
+  "files": [],
   "dependencies": {
     "@prettier/plugin-xml": "^2.2.0",
     "@typescript-eslint/eslint-plugin": "^5.25.0",
@@ -16,12 +17,12 @@
     "eslint": "^8.15.0",
     "eslint-config-airbnb-base": "^15.0.0",
     "eslint-config-airbnb-typescript": "^17.0.0",
-    "eslint-config-isaacscript": "^1.0.76",
+    "eslint-config-isaacscript": "^1.0.79",
     "eslint-config-prettier": "^8.5.0",
     "eslint-plugin-eslint-comments": "^3.2.0",
     "eslint-plugin-import": "^2.26.0",
-    "eslint-plugin-isaacscript": "^1.0.39",
-    "eslint-plugin-jsdoc": "^39.2.9",
+    "eslint-plugin-isaacscript": "^1.0.40",
+    "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",

package/.cspell.json

@@ -1,18 +0,0 @@
-{
-    "version": "0.2",
-    "words": [
-        "dbaeumer",
-        "eqeqeq",
-        "esbenp",
-        "gofmt",
-        "gofmt's",
-        "Gruntfile",
-        "isaacscript",
-        "prettier's",
-        "rossum",
-        "rustfmt",
-        "tiamtowtdi",
-        "unexported",
-        "zamiell"
-    ]
-}

package/.gitattributes

@@ -1,9 +0,0 @@
-# Prevent Windows systems from cloning this repository with "\r\n" line endings
-core.autocrlf=false
-
-# Prevent people from making merge commits
-# https://www.endoflineblog.com/gitflow-considered-harmful
-pull.rebase=true
-
-# Convert all files to use "\n" line endings
-* text=auto eol=lf

package/.vscode/extensions.json

@@ -1,8 +0,0 @@
-// These are Visual Studio Code extensions that are intended to be used with this particular
-// repository
-// https://go.microsoft.com/fwlink/?LinkId=827846
-{
-  "recommendations": [
-    "streetsidesoftware.code-spell-checker", // A spell-checker extension based on cspell
-  ]
-}

package/.vscode/settings.json

@@ -1,16 +0,0 @@
-// These are Visual Studio Code settings that should apply to this particular repository
-{
-  // ----------------
-  // Vanilla settings
-  // ----------------
-
-  // This matches the Airbnb JavaScript style guide
-  "editor.rulers": [100],
-  "editor.tabSize": 2,
-
-  // Linux line endings are used in this project
-  "files.eol": "\n",
-
-  // Automatically removing all trailing whitespace when saving a file
-  "files.trimTrailingWhitespace": true,
-}

package/nuke.sh

@@ -1,18 +0,0 @@
-#!/bin/bash
-
-set -e # Exit on any errors
-
-# Get the directory of this script
-# https://stackoverflow.com/questions/59895/getting-the-source-directory-of-a-bash-script-from-within
-DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
-
-PACKAGE_LOCK="$DIR/package-lock.json"
-rm -f "$PACKAGE_LOCK"
-echo "Successfully deleted: $PACKAGE_LOCK"
-
-NODE_MODULES="$DIR/node_modules"
-rm -rf "$NODE_MODULES"
-echo "Successfully deleted: $NODE_MODULES"
-
-npm install
-echo "Successfully reinstalled Node depedencies."

package/publish.sh

@@ -1,11 +0,0 @@
-#!/bin/bash
-
-set -e # Exit on any errors
-
-# Get the directory of this script
-# https://stackoverflow.com/questions/59895/getting-the-source-directory-of-a-bash-script-from-within
-DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
-
-cd "$DIR"
-pip install publish-npm --upgrade --quiet
-publish-npm "$@"

package/update.sh

@@ -1,17 +0,0 @@
-#!/bin/bash
-
-set -e # Exit on any errors
-
-# Get the directory of this script
-# https://stackoverflow.com/questions/59895/getting-the-source-directory-of-a-bash-script-from-within
-DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
-
-cd "$DIR"
-
-PACKAGE_JSON="$DIR/package.json"
-OLD_HASH=$(md5sum "$PACKAGE_JSON")
-npx npm-check-updates --upgrade --packageFile "$PACKAGE_JSON"
-NEW_HASH=$(md5sum "$PACKAGE_JSON")
-if [[ $OLD_HASH != $NEW_HASH ]]; then
-  npm install
-fi