linter-bundle 6.3.0 → 7.0.0

package/stylelint/plugins/stylelint-selector-tag-no-without-class.js

@@ -1,3 +1,5 @@
+/* eslint-disable -- We want to keep as much of the original code as possible */
+
 /**
  * @file Fork of `stylelint-selector-tag-no-without-class` rule.
  *
@@ -6,8 +8,6 @@
  * @see https://github.com/Moxio/stylelint-selector-tag-no-without-class
  */
 
-/* eslint-disable jsdoc/require-jsdoc -- Unfortunately, this is not given in the original code. */
-
 import stylelint from 'stylelint';
 // @ts-expect-error -- No declaration file.
 import isStandardSyntaxRule from 'stylelint/lib/utils/isStandardSyntaxRule.mjs';

package/stylelint.mjs

@@ -0,0 +1,6 @@
+/**
+ * @file Wrapper which allows to extend "linter-bundle/stylelint.mjs" instead of "linter-bundle/stylelint/index.mjs"
+ */
+
+export { default } from './stylelint/index.mjs';
+

package/TODO.md

@@ -1,58 +0,0 @@
-# @todo
-
-- Aktuell sind die Versionen von den Audit-Tools hardcodiert in der lint.js hinterlegt:
-  'better-npm-audit@3.7.3',
-  'improved-yarn-audit@3.0.0',
-  Das sollte irgendwo hinterlegt werden, so z.B. check-outdated drauf zugreifen kann. (z.B. die optionalDependencies? Sind diese nach dem regulären Installieren noch vorhanden und lassen sich entsprechend auslesen? Werden diese von check-outdated geprüft?)
-
-- Timing funktioniert nicht - siehe HexEd.it-core
-
-- Wie erreichen wir auto-completion in der .linter-bundle.js datei?
-  .linter-bundle.json vielleicht mit Schema-Datei?
-
-<!-- markdownlint-disable -->
-
-- Bereiche in Readme aufklappbar machen:
-<details>
- summary>yarn</summary>
-
-```shell
-yarn add click-to-react-component
-```
-</details>
-
-- Make git diff-branch configurable  
-  on GitHub Actions this could be used:  
-  - run: git diff --name-only -z origin/${GITHUB_BASE_REF}  
-  Is there a variable with includes origin/ already?
-
-Some tools like Gatsby ship deprecated dependencies of eslint and @typescript-eslint.  
-Since npm installs packages alphabetically, the outdated `gatsby` dependencies are installed in the `node_modules` root, instead of the newer `linter-bundle` dependencies. Since the old versions often do not support new rules or new options, this may cause linting to fail with errors like this:
-
-```bash
-Error while loading rule 'import/no-unused-modules': .eslintrc.js » ./node_modules/linter-bundle/eslint/index.js:
-Configuration for rule "@typescript-eslint/no-throw-literal" is invalid:
-Value [{"allowThrowingAny":false,"allowThrowingUnknown":true}] should NOT have more than 0 items.
-```
-
-To solve such problems, npm supports [`overrides`](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) as of version [8.3](https://github.com/npm/cli/releases/tag/v8.3.0), while yarn supports [`resolutions`](https://classic.yarnpkg.com/en/docs/selective-version-resolutions/).
-
-By using the `enforce-deps` option, linter-bundle will ensure the right versions of the dependencies are installed, and if not it automatically write these options to your package.json and then run an `npm i` or `yarn`, before starting the linting to ensure that the correct dependency versions are installed.
-
-```json
-"overrides": {
-  "@typescript-eslint/eslint-plugin": "$linter-bundle",
-  "@typescript-eslint/parser": "$linter-bundle",
-  "eslint": "$linter-bundle"
-}
-```
-
-- Option to lint only changed files in Git
-  - [lint-staged](https://github.com/okonet/lint-staged)
-  - [affected](https://www.npmjs.com/package/affected)
-  - [git-affected-files](https://www.npmjs.com/package/git-affected-files)
-  - [affected-files](https://www.npmjs.com/package/affected-files)
-  - [is-affected](https://www.npmjs.com/package/is-affected)
-
-- Find stylelint rule which checks for wrong values like:  
-  `padding-top: 3px 3px 0;`