Troubleshooting
Some tips in case of problems:
There is no pdf and / or docx buttonβ
This is normal behavior. The download buttons only appear when the corresponding PDF and/or DOCX files actually exist in your docs/ folder.
Solution: Export your specification to PDF and/or DOCX format first:
- Run
npm run menuin your project - Select option
[2] Export to PDF(to generateindex.pdf) - Select option
[3] Export to DOCX(to generateindex.docx) - Refresh your specification page in the browser
Once the files exist, the download buttons will automatically appear in the top navigation bar next to the theme toggle button.
Note: The buttons are intentionally only shown when files exist to avoid displaying broken download links.
GitHub and API and limitsβ
Problem: I want to look up an external reference (xref) but I get an error about GitHub and API and limits.
Solution: get a GitHub Token.
I am sure an external reference contains the term I am referencing, but it does not showβ
Maybe the repository is not indexed by GitHub. Do a manual search on the term:
- Go to the repository
- Enter your search term in the search field that shows: βType / to searchβ and enter.
If you see this: *βThis repository's code has not been indexed yet. Try again later.β * the repository has not been indexed (yet).
You cannot directly trigger the indexing, but making a change by committing something helps.
WSL2 usersβ
WSL2 users are recommended to use the bash option rather than PowerShell in the terminal of Visual Studio Code.
Use Node.js versions 18+β
Spec-Up-T uses fetch, which was added in version 18.
Install NVM if you haven't already. (Instructions not given here).
Then run Node.js version 18.
Cache Issuesβ
Problem: Persistent build or rendering issues.
Solution: Remove the .cache directory and rerender the site.
- Windows: Open File Explorer, navigate to the project root directory, and delete the
.cachefolder - Mac: Open Finder, navigate to the project root directory, and delete the
.cachefolder - Linux (Ubuntu): Open the file manager (e.g., Files), navigate to the project root directory, and delete the
.cachefolder
If using the terminal command rm -rf, be cautious as it is powerful and irreversible. For safer options, use your system's file explorer or manager.