Warning when running for a fresh site

[damithc]

version: v7.0.0

Commands:

markbind init
markbind serve -o

Output:

Are these warnings/errors expected?

[damithc]

I tried v7.0.0 with the CS2103 website. It seems PlantUML and Mermaid diagrams are not working.

Do I need to update the node version?

[gerteck]

Yes, maybe we can add a node version guard check to exit early below node v22.22 in a minor release, advice to use v6 if using a lower node version

[damithc]

With @gerteck's help, we traced the warnings to an outdated node version I had.

The errors seems to be related to the PageFind feature, and is persistent even after updating the node version. @MoshiMoshiMochi have a look when you have time.

[damithc]

The errors seems to be related to the PageFind feature, and is persistent even after updating the node version. @MoshiMoshiMochi have a look when you have time.

In fact it is because these pages don't exist when using -o flag. I think we should not show those as errors in the console, as missing pages is expected when using -o mode.

[MoshiMoshiMochi]

Noted. Will investigate further on this issue to fix it.

[damithc]

@MoshiMoshiMochi If the site is not using PageFind search, do we still build the PageFind index?

[MoshiMoshiMochi]

Hi Prof @damithc, yes! Not using Pagefind search will skip its indexing during the build.

As PageFind search is tied to enableSearch option in site.json (which is true by default), the only way to not use PageFind search would be to set it to false. This would skip all Pagefind related things during the build.

However, as enableSearch is also tied to our current built-in search, setting it to false would inherently disable it as well. Since Pagefind is still an incomplete feature, let me know if you would prefer to create a temporary option to toggle Pagefind search instead, or if you feel the current enableSearch option is fine.