markdownlint 0.26.2 → 0.28.0

package/CHANGELOG.md

@@ -0,0 +1,378 @@
+# Changelog
+
+## 0.28.0
+
+- Introduce `micromark` parser for better positional data (internal only)
+- Use `micromark` in MD013/MD033/MD034/MD035/MD038/MD044/MD052/MD053
+- Simplify file-based test cases
+- Unify browser script for demo
+- Update dependencies
+
+## 0.27.0
+
+- Improve MD011/MD013/MD022/MD031/MD032/MD033/MD034/MD040/MD043/MD051/MD053
+- Generate/separate documentation
+- Improve documentation
+- Update dependencies
+
+## 0.26.2
+
+- Improve MD037/MD051/MD053
+
+## 0.26.1
+
+- Improve MD051
+
+## 0.26.0
+
+- Add MD051/MD052/MD053 for validating link fragments & reference
+  links/images & link/image reference definitions (MD053 auto-fixable)
+- Improve MD010/MD031/MD035/MD039/MD042/MD044/MD049/MD050
+- Add `markdownlint-disable-line` inline comment
+- Support `~` paths in `readConfig/Sync`
+- Add `configParsers` option
+- Remove support for end-of-life Node version 12
+- Default `resultVersion` to 3
+- Update browser script to use ES2015
+- Simplify JSON schema
+- Address remaining CodeQL issues
+- Improve performance
+- Update dependencies
+
+## 0.25.1
+
+- Update dependencies for CVE-2022-21670
+
+## 0.25.0
+
+- Add MD049/MD050 for consistent emphasis/strong style (both auto-fixable)
+- Improve MD007/MD010/MD032/MD033/MD035/MD037/MD039
+- Support asynchronous custom rules
+- Improve performance
+- Improve CI process
+- Reduce dependencies
+- Update dependencies
+
+## 0.24.0
+
+- Remove support for end-of-life Node version 10
+- Add support for custom file system module
+- Improve MD010/MD011/MD037/MD043/MD044
+- Improve TypeScript declaration file and JSON schema
+- Update dependencies
+
+## 0.23.1
+
+- Work around lack of webpack support for dynamic calls to `require`(`.resolve`)
+
+## 0.23.0
+
+- Add comprehensive example `.markdownlint.jsonc`/`.markdownlint.yaml` files
+- Add fix information for MD004/ul-style
+- Improve MD018/MD019/MD020/MD021/MD037/MD041
+- Improve HTML comment handling
+- Update test runner and test suite
+- Update dependencies
+
+## 0.22.0
+
+- Allow `extends` in config to reference installed packages by name
+- Add `markdownlint-disable-next-line` inline comment
+- Support JSON front matter
+- Improve MD009/MD026/MD028/MD043
+- Update dependencies (including `markdown-it` to v12)
+
+## 0.21.1
+
+- Improve MD011/MD031
+- Export `getVersion` API
+
+## 0.21.0
+
+- Lint concurrently for better performance (async only)
+- Add Promise-based APIs
+- Update TypeScript declaration file
+- Hide `toString` on `LintResults`
+- Add ability to fix in browser demo
+- Allow custom rules in `.markdownlint.json` schema
+- Improve MD042/MD044
+- Improve documentation
+- Update dependencies
+
+## 0.20.4
+
+- Fix regression in MD037
+- Improve MD034/MD044
+- Improve documentation
+
+## 0.20.3
+
+- Fix regression in MD037
+- Improve MD044
+- Add automatic regression testing
+
+## 0.20.2
+
+- Fix regression in MD037
+- Improve MD038
+
+## 0.20.1
+
+- Fix regression in MD037
+
+## 0.20.0
+
+- Add `markdownlint-configure-file` inline comment
+- Reimplement MD037
+- Improve MD005/MD007/MD013/MD018/MD029/MD031/MD034/MD038/MD039
+- Improve HTML comment handling
+- Update dependencies
+
+## 0.19.0
+
+- Remove support for end-of-life Node version 8
+- Add fix information for MD005/list-indent
+- Improve MD007/MD013/MD014
+- Deprecate MD006/ul-start-left
+- Add rationale for every rule
+- Update test runner and code coverage
+- Add more JSDoc comments
+- Update dependencies
+
+## 0.18.0
+
+- Add MD048/code-fence-style
+- Add fix information for MD007/ul-indent
+- Add `markdownlint-disable-file`/`markdownlint-enable-file` inline comments
+- Add type declaration file (.d.ts) for TypeScript dependents
+- Update schema
+- Improve MD006/MD007/MD009/MD013/MD030
+- Update dependencies
+
+## 0.17.2
+
+- Improve MD020/MD033/MD044
+
+## 0.17.1
+
+- Fix handling of front matter by fix information
+
+## 0.17.0
+
+- Add `resultVersion` 3 to support fix information for default and custom rules
+- Add fix information for 24 rules
+- Update newline handling to match latest CommonMark specification
+- Improve MD014/MD037/MD039
+- Update dependencies
+
+## 0.16.0
+
+- Add custom rule sample for linting code
+- Improve MD026/MD031/MD033/MD038
+- Update dependencies
+
+## 0.15.0
+
+- Add `markdownlint-capture`/`markdownlint-restore` inline comments
+- Improve MD009/MD013/MD026/MD033/MD036
+- Update dependencies
+
+## 0.14.2
+
+- Improve MD047
+- Add `handleRuleFailures` option
+
+## 0.14.1
+
+- Improve MD033
+
+## 0.14.0
+
+- Remove support for end-of-life Node version 6
+- Introduce `markdownlint-rule-helpers`
+- Add MD046/MD047
+- Improve MD033/MD034/MD039
+- Improve custom rule validation and in-browser demo
+- Update dependencies
+
+## 0.13.0
+
+- Improve MD013/MD022/MD025/MD029/MD031/MD032/MD037/MD041
+- Deprecate MD002
+- Improve Pandoc YAML support
+- Update dependencies
+
+## 0.12.0
+
+- Add `information` link for custom rules
+- Add `markdownItPlugins` for extensibility
+- Improve MD023/MD032/MD038
+- Update dependencies
+
+## 0.11.0
+
+- Improve MD005/MD024/MD029/MD038
+- Improve custom rule example
+- Add `CONTRIBUTING.md`
+- Update dependencies
+
+## 0.10.0
+
+- Add support for non-JSON configuration files
+- Pass file/string name to custom rules
+- Update dependencies
+
+## 0.9.0
+
+- Remove support for end-of-life Node versions 0.10/0.12/4
+- Change "header" to "heading" per spec (non-breaking)
+- Improve MD003/MD009/MD041
+- Handle uncommon line-break characters
+- Refactor for ES6
+- Update dependencies
+
+## 0.8.1
+
+- Update item loop to be iterative
+- Improve MD014
+- Update dependencies
+
+## 0.8.0
+
+- Add support for using and authoring custom rules
+- Improve MD004/MD007/MD013
+- Add `engines` to `package.json`
+- Refactor
+- Update dependencies
+
+## 0.7.0
+
+- `resultVersion` defaults to 2 (breaking change)
+- Add MD045
+- Improve MD029
+- Remove `trimLeft`/`trimRight`
+- Split rules
+- Refactor
+- Update dependencies
+
+## 0.6.4
+
+- Improve MD029/MD042
+- Update dependencies
+
+## 0.6.3
+
+- Improve highlighting for MD020
+
+## 0.6.2
+
+- Improve MD013/MD027/MD034/MD037/MD038/MD041/MD044
+- Update dependencies
+
+## 0.6.1
+
+- Update `markdown-it` versioning
+- Exclude demo/test from publishing
+
+## 0.6.0
+
+- `resultVersion` defaults to 1 (breaking change)
+- Ignore HTML comments
+- TOML front matter
+- Fixes for MD044
+- Update dependencies
+
+## 0.5.0
+
+- Add shareable configuration
+- Add `noInlineConfig` option
+- Add `README.md` links
+- Fix MD030
+- Improve MD009/MD041
+- Update dependencies
+
+## 0.4.1
+
+- Fixes for MD038/front matter
+- Improvements to MD044
+- Update dependencies
+
+## 0.4.0
+
+- Add MD044
+- Enhance MD013/MD032/MD041/MD042/MD043
+- Fix for MD038
+- Update dependencies
+
+## 0.3.1
+
+- Fix regressions in MD032/MD038
+- Update dependencies
+
+## 0.3.0
+
+- More detailed error reporting with `resultVersion`
+- Enhance MD010/MD012/MD036
+- Fixes for MD027/MD029/MD030
+- Include JSON schema dependencies
+
+## 0.2.0
+
+- Add MD042/MD043
+- Enhance MD002/MD003/MD004/MD007/MD011/MD025/MD041
+- Update dependencies
+
+## 0.1.1
+
+- Fix bug handling HTML in tables
+- Reference `markdownlint-cli`
+
+## 0.1.0
+
+- Add aliases
+- Exceptions for MD033
+- Exclusions for MD013
+- Update dependencies
+
+## 0.0.8
+
+- Support disabling/enabling rules inline
+- Improve code fence
+- Update dependencies
+
+## 0.0.7
+
+- Add MD041
+- Improve MD003
+- Ignore front matter
+- Update dependencies
+
+## 0.0.6
+
+- Improve performance
+- Simplify in-browser
+- Update dependencies
+
+## 0.0.5
+
+- Add `strings` option to enable file-less scenarios
+- Add in-browser demo
+
+## 0.0.4
+
+- Add tests MD033-MD040
+- Update dependencies
+
+## 0.0.3
+
+- Add synchronous API
+- Improve documentation and code
+
+## 0.0.2
+
+- Improve documentation, tests, and code
+
+## 0.0.1
+
+- Initial release
+- Includes tests MD001-MD032

package/CONTRIBUTING.md

@@ -1,63 +1,86 @@
 # Contributing
 
-Interested in contributing? Great! Here are some suggestions to make it a good experience:
-
-Start by [opening an issue](https://github.com/DavidAnson/markdownlint/issues), whether to identify a problem or outline a change.
-That issue should be used to discuss the situation and agree on a plan of action before writing code or sending a pull request.
-Maybe the problem isn't really a problem, or maybe there are more things to consider.
-If so, it's best to realize that before spending time and effort writing code that may not get used.
-
-Match the coding style of the files you edit.
-Although everyone has their own preferences and opinions, a pull request is not the right forum to debate them.
-
-Do not add new [`dependencies` to `package.json`](https://docs.npmjs.com/files/package.json#dependencies).
-The excellent Markdown parser [markdown-it](https://www.npmjs.com/package/markdown-it) is this project's one and only dependency.
-
-If developing a new rule, start by creating a [custom rule](doc/CustomRules.md) in its own project.
-Once written, published, and tested in real world scenarios, open an issue to consider adding it to this project.
-For rule ideas, see [issues tagged with the `new rule` label](https://github.com/DavidAnson/markdownlint/labels/new%20rule).
-
-Add tests for all new/changed functionality.
-Test positive and negative scenarios.
-Try to break the new code now, or else it will get broken later.
-
-Run tests before sending a pull request via `npm test` in the [usual manner](https://docs.npmjs.com/misc/scripts).
-Tests should all pass on all platforms.
-The test runner is [AVA](https://github.com/avajs/ava) and test cases are located in `test/markdownlint-test*.js`.
-When running tests, `test/*.md` files are enumerated, linted, and fail if any violations are missing a corresponding `{MD###}` marker in the test file.
-For example, the line `### Heading {MD001}` is expected to trigger the rule `MD001`.
-For cases where the marker text can not be present on the same line, the syntax `{MD###:#}` can be used to include a line number.
-If `some-test.md` needs custom configuration, a `some-test.json` is used to provide a custom `options.config` for that scenario.
-Tests run by `markdownlint-test-scenarios.js` use [AVA's snapshot feature](https://github.com/avajs/ava/blob/main/docs/04-snapshot-testing.md).
-To update snapshots (for example, after modifying a test file), run `npm run update-snapshots` and include the updated files with the pull request.
-
-Lint before sending a pull request by running `npm run lint`.
-There should be no issues.
-
-Run a full continuous integration pass before sending a pull request via `npm run ci`.
-Code coverage should always be 100%.
-As part of a continuous integration run, generated files may get updated and fail the run - commit them to the repository and rerun continuous integration.
-
-Pull requests should contain a single commit.
-If necessary, squash multiple commits before creating the pull request and when making changes.
-(See [Git Tools - Rewriting History](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) for details.)
-
-Open pull requests against the `next` branch.
-That's where the latest changes are staged for the next release.
-Include the text "(fixes #??)" at the end of the commit message so the pull request will be associated with the relevant issue.
-End commit messages with a period (`.`).
-Once accepted, the tag `fixed in next` will be added to the issue.
-When the commit is merged to the main branch during the release process, the issue will be closed automatically.
-(See [Closing issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/) for details.)
-
-Please refrain from using slang or meaningless placeholder words.
-Sample content can be "text", "code", "heading", or the like.
-Sample URLs should use [example.com](https://en.wikipedia.org/wiki/Example.com) which is safe for this purpose.
-Profanity is not allowed.
-
-In order to maintain the permissive MIT license this project uses, all contributions must be your own and released under that license.
-Code you add should be an original work and should not be copied from elsewhere.
-Taking code from a different project, Stack Overflow, or the like is not allowed.
-The use of tools such as GitHub Copilot that generate code from other projects is not allowed.
+Interested in contributing? Great! Here are some suggestions to make it a good
+experience:
+
+Start by [opening an issue](https://github.com/DavidAnson/markdownlint/issues),
+whether to identify a problem or outline a change. That issue should be used to
+discuss the situation and agree on a plan of action before writing code or
+sending a pull request. Maybe the problem isn't really a problem, or maybe there
+are more things to consider. If so, it's best to realize that before spending
+time and effort writing code that may not get used.
+
+Match the coding style of the files you edit. Although everyone has their own
+preferences and opinions, a pull request is not the right forum to debate them.
+
+Do not add new [`dependencies` to `package.json`][dependencies]. The Markdown
+parsers [`markdown-it`][markdown-it] and [`micromark`][micromark] are the
+project's only dependencies.
+
+If developing a new rule, start by creating a [custom rule][custom-rules] in its
+own project. Once written, published, and tested in real world scenarios, open
+an issue to consider adding it to this project. For rule ideas, see [issues
+tagged with the `new rule` label][new-rule].
+
+Add tests for all new/changed functionality. Test positive and negative
+scenarios. Try to break the new code now, or else it will get broken later.
+
+Run tests before sending a pull request via `npm test` in the [usual
+manner][npm-scripts]. Tests should all pass on all platforms. The test runner is
+[AVA][ava] and test cases are located in `test/markdownlint-test*.js`. When
+running tests, `test/*.md` files are enumerated, linted, and fail if any
+violations are missing a corresponding `{MD###}` marker in the test file. For
+example, the line `### Heading {MD001}` is expected to trigger the rule `MD001`.
+For cases where the marker text can not be present on the same line, the syntax
+`{MD###:#}` can be used to include a line number. If `some-test.md` needs custom
+configuration, a `some-test.json` is used to provide a custom `options.config`
+for that scenario. Tests run by `markdownlint-test-scenarios.js` use [AVA's
+snapshot feature][ava-snapshots]. To update snapshots (for example, after
+modifying a test file), run `npm run update-snapshots` and include the updated
+files with the pull request.
+
+Lint before sending a pull request by running `npm run lint`. There should be no
+issues.
+
+Run a full continuous integration pass before sending a pull request via `npm
+run ci`. Code coverage should always be 100%. As part of a continuous
+integration run, generated files may get updated and fail the run - commit them
+to the repository and rerun continuous integration.
+
+Pull requests should contain a single commit. If necessary, squash multiple
+commits before creating the pull request and when making changes. (See [Git
+Tools - Rewriting History][rewriting-history] for details.)
+
+Open pull requests against the `next` branch. That's where the latest changes
+are staged for the next release. Include the text "(fixes #??)" at the end of
+the commit message so the pull request will be associated with the relevant
+issue. End commit messages with a period (`.`). Once accepted, the tag `fixed in
+next` will be added to the issue. When the commit is merged to the main branch
+during the release process, the issue will be closed automatically. (See
+[Closing issues using keywords][closing-keywords] for details.)
+
+Please refrain from using slang or meaningless placeholder words. Sample content
+can be "text", "code", "heading", or the like. Sample URLs should use
+[example.com][example-com] which is safe for this purpose. Profanity is not
+allowed.
+
+In order to maintain the permissive MIT license this project uses, all
+contributions must be your own and released under that license. Code you add
+should be an original work and should not be copied from elsewhere. Taking code
+from a different project, Stack Overflow, or the like is not allowed. The use of
+tools such as GitHub Copilot that generate code from other projects is not
+allowed.
 
 Thank you!
+
+[ava]: https://github.com/avajs/ava
+[ava-snapshots]: https://github.com/avajs/ava/blob/main/docs/04-snapshot-testing.md
+[closing-keywords]: https://help.github.com/articles/closing-issues-using-keywords/
+[custom-rules]: doc/CustomRules.md
+[dependencies]: https://docs.npmjs.com/files/package.json#dependencies
+[example-com]: https://en.wikipedia.org/wiki/Example.com
+[markdown-it]: https://www.npmjs.com/package/markdown-it
+[micromark]: https://www.npmjs.com/package/micromark
+[new-rule]: https://github.com/DavidAnson/markdownlint/labels/new%20rule
+[npm-scripts]: https://docs.npmjs.com/misc/scripts
+[rewriting-history]: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

package/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015-2022 David Anson
+Copyright (c) David Anson
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal