This script reads in a folder of Markdown files, notes all the [wiki-style links] between them, then adds a special "backlinks" section which lists passages which reference a given file.
For example, this text might get added to
## Backlinks * [[Something that links here]] * The block of text in the referencing note which contains the link to [[Sample note]]. * Another block in that same note which links to [[Sample note]]. * [[A different note that links here]] * This is a paragraph from another note which links to [[Sample note]].
The script is idempotent; on subsequent runs, it will update that backlinks section in-place.
The backlinks section will be initially inserted at the end of the file. If there happens to be a HTML-style
<!-- --> block at the end of your note, the backlinks will be inserted before that block.
- Links are formatted
- Note titles are inferred from filenames. That is: if a file named
Note A.mdcontains the text
[[Note B]], then a backlink to
Note Awill be added to the file named
Note B.md. No special handling is yet present for special characters in filenames.
.mdfiles are siblings; the script does not currently recursively traverse subtrees (though that would be a simple modification if you need it; see
- The backlinks "section" is defined as the AST span between
## Backlinksand the next heading tag (or
<!-- -->tag). Any text you might add to this section will be clobbered. Don't append text after the backlinks list without a heading in between! (I like to leave my backlinks list at the end of the file)
This is FYI-style open source
This is FYI-style open source. I'm sharing it for interested parties, but without any stewardship commitment. Assume that my default response to issues and pull requests will by to ignore or close them without comment. If you do something interesting with this, though, please let me know.
To install a published release, run:
yarn global add @andymatuschak/note-link-janitor
Then to run it (note that it will modify your
.md files in-place; you may want to make a backup!):
That will run it once; you'll need to create a cron job or a launch daemon to run it regularly.
It's built to run against Node >=12, so you may need to upgrade or swap your runtime version.
Building a local copy
yarn install yarn run build
In the future, I intend to expand this project to monitor for broken links, orphans, and other interesting hypertext-y predicates.