You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the image: false option has produced the following error for me, under Quarto version 1.4.549
ERROR: TypeError: path.startsWith is not a function
Stack trace:
at listingItemHref (file:///opt/quarto/bin/quarto.js:89130:37)
at listItemFromFile (file:///opt/quarto/bin/quarto.js:88951:71)
at eventLoopTick (ext:core/01_core.js:183:11)
at async readContents (file:///opt/quarto/bin/quarto.js:88780:34)
at async readListings (file:///opt/quarto/bin/quarto.js:88416:36)
at async listingHtmlDependencies (file:///opt/quarto/bin/quarto.js:90080:45)
at async Object.formatExtras (file:///opt/quarto/bin/quarto.js:90400:45)
at async runPandoc (file:///opt/quarto/bin/quarto.js:68741:63)
at async renderPandoc (file:///opt/quarto/bin/quarto.js:70041:26)
at async Object.onRender (file:///opt/quarto/bin/quarto.js:77261:36)
I was able to disable images in the listing by setting image-height: "0" in the listing options.
In addition, once the error is resolved, false doesn't prevent the image from being used as a preview. The below (which is in the default quarto blog project).
---
title: "Welcome To My Blog"
author: "Tristan O'Malley"
date: "2024-02-09"
categories: [news]
image: false
---
This is the first post in a Quarto blog. Welcome!
![](thumbnail.jpg)
Since this post doesn't specify an explicit `image`, the first image in the post will be used in the listing page of posts.
The text was updated successfully, but these errors were encountered:
Using the
image: false
option has produced the following error for me, under Quarto version 1.4.549I was able to disable images in the listing by setting
image-height: "0"
in the listing options.In addition, once the error is resolved,
false
doesn't prevent the image from being used as a preview. The below (which is in the default quarto blog project).The text was updated successfully, but these errors were encountered: