mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 09:46:01 +03:00
[GH-ISSUE #928] Why there are no binary/executable? #2402
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#2402
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jcubic on GitHub (Aug 10, 2023).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/928
Why provide only the NodeJS module? This is a common thing to run the executable. In order to add lint to the pre-commit hook I need to create an executable. It would be much more useful if there was a binary.
The first thing I did after the installation was use
npx markdownlintwhich give an error, next was searching node_module/.bin for the binary.@nschonni commented on GitHub (Aug 10, 2023):
The CLIs are the executable versions https://github.com/DavidAnson/markdownlint#related
@DavidAnson commented on GitHub (Aug 10, 2023):
Distributing the library as a standalone package along with another package for the command-line interface is a pretty common pattern in the Node.js ecosystem.
Regarding your workflow, if you are going to use NPX, then you do not need to also install the package.
As Nick points out, there are two CLI options for this library: a more traditional one (markdownlint-cli)and an alternative (markdownlint-cli2).
@jcubic commented on GitHub (Aug 10, 2023):
Thanks for your quick response, I just assumed that those were similar but different projects.