Fix link checker by moving configuration to lychee.toml file

[Copilot]

The link checker was failing with 9 errors because it was trying to validate URLs in _static/webpack-macros.html that contain unprocessed Jinja2 template variables. This file is generated by the quantecon_book_theme during the Jupyter Book build process but contains template syntax like:

{{ pathto('_static/scripts/bootstrap.js', 1) }}
{{ pathto('_static/styles/pydata-sphinx-theme.css', 1) }}
{{ pathto('_static/vendor/fontawesome/6.5.2/css/all.min.css', 1) }}

The link checker was interpreting these template variables as literal file URLs, causing "Cannot find file" errors for all 9 template references in the file.

Solution

Created a lychee.toml configuration file to centralize lychee settings and exclude _static/webpack-macros.html. This approach is cleaner and more maintainable than using command-line parameters in the workflow file. The configuration file includes:

• Exclusion of the problematic template file with clear documentation
• Acceptance of 403 and 503 HTTP status codes
• Version-controlled settings that can be easily modified

This prevents false positive errors while maintaining link checking for all legitimate content files.

Fixes #248.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[netlify]

✅ Deploy Preview for lustrous-melomakarona-3ee73e ready!

Name	Link
🔨 Latest commit	41923a0
🔍 Latest deploy log	https://app.netlify.com/projects/lustrous-melomakarona-3ee73e/deploys/68abce4d9f24a00007c24acd
😎 Deploy Preview	https://deploy-preview-249--lustrous-melomakarona-3ee73e.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mmcky]

@copilot is there a way to specify this in a lychee toml or yaml configuration file?

[Copilot]

@copilot is there a way to specify this in a lychee toml or yaml configuration file?

Yes! I've moved the configuration to a lychee.toml file which is cleaner and more maintainable. Lychee automatically picks up the configuration from this file, so we no longer need the command-line arguments in the workflow. The configuration file includes the same settings (accepting 403/503 status codes and excluding the webpack-macros.html file) with clear documentation. See commit 41923a0.

[github-actions]

🚀 Deployed on https://68abd377902af1a33373a7be--lustrous-melomakarona-3ee73e.netlify.app