[GH-ISSUE #332] Allow configuration to be read from package.json #2135

New issue

Closed

opened 2026-03-07 20:04:55 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:04:55 +03:00

Owner

Originally created by @ylavoie on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/332

Many Linters allow their configuration to be read from a key in package.json. JS & CSS linters, for example. Allowing Markdownlint to read its config from a 'markdownlint' key would consistent with others.
This simplifies maintenance by regrouping all relevant configs in a single file.

Originally created by @ylavoie on GitHub (Sep 28, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/332 Many Linters allow their configuration to be read from a key in package.json. JS & CSS linters, for example. Allowing Markdownlint to read its config from a 'markdownlint' key would consistent with others. This simplifies maintenance by regrouping all relevant configs in a single file.

kerem

2026-03-07 20:04:55 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-07 20:04:56 +03:00

Author

Owner

@DavidAnson commented on GitHub (Sep 29, 2020):

Do you mean to open this issue for one of the CLI packages? The library (this package) doesn’t read configuration from anywhere - it requires the caller to pass it in from wherever the caller wants to get it.

@DavidAnson commented on GitHub (Sep 29, 2020): Do you mean to open this issue for one of the CLI packages? The library (this package) doesn’t read configuration from anywhere - it requires the caller to pass it in from wherever the caller wants to get it.

kerem commented

2026-03-07 20:04:56 +03:00

Author

Owner

@DavidAnson commented on GitHub (Oct 21, 2020):

This approach isn't really consistent with the goals of markdownlint-cli2, but it might be good for markdownlint-cli here: https://github.com/igorshubovych/markdownlint-cli

@DavidAnson commented on GitHub (Oct 21, 2020): This approach isn't really consistent with the goals of `markdownlint-cli2`, but it might be good for `markdownlint-cli` here: https://github.com/igorshubovych/markdownlint-cli