Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tags.md not always processed last

Open
#5 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Reproduce the issue with the provided table of contents and run a GitBook build. Inspect how the plugin determines page-processing order, especially when tags.md is linked directly. Done means tags.html includes tags from item2.md regardless of the tags.md link format.

Written by the indexing model from the issue text.

Description

I found that linking to tags.md will make it not be processed last. This made tags.html content incomplete after a gitbook build.

# Table of Contents

* [item1](/tags.md#item1)
* [item2](/item2.md)
* [tags](tags.md)

In the above example, any tags in item2 will not show after a gitbook build.

There is a workaround, but I thought I'd post it here, since it took me a while to track down.

Dominant language
JavaScript
Stars
25
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from billryan/gitbook-plugin-tags

All issues in billryan/gitbook-plugin-tags

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.