quarto-dev / quarto-dev/quarto-cli

`quarto render` should prints resources not found as `quarto preview` (via web server)

Open
#10,484 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Take:

---
title: "Quarto Playground"
format: html
---

This is a playground for Quarto.

![An image](wrong/path/to/image.png){#fig-placeholder}
quarto renderquarto preview
pandoc 
  to: html
  output-file: index.html
  standalone: true
  section-divs: true
  html-math-method: mathjax
  wrap: none
  default-image-extension: png
  
metadata
  document-css: false
  link-citations: true
  date-format: long
  lang: en
  title: Quarto Playground
  
Output created: index.html
andoc 
  to: html
  output-file: index.html
  standalone: true
  section-divs: true
  html-math-method: mathjax
  wrap: none
  default-image-extension: png
  
metadata
  document-css: false
  link-citations: true
  date-format: long
  lang: en
  title: Quarto Playground
  
Output created: index.html

Watching files for changes
Browse at http://localhost:3317/index.html
  /wrong/path/to/image.png (404: Not Found)

Currently, the "not found" is the result of the web server as --no-browser would lead to the same output as quarto render (as expected).

quarto preview index.qmd --no-browser

Contributor guide

Open the contributing guide

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.

Research direction

Start with the supplied index.qmd example and compare the output of quarto render with quarto preview, including quarto preview index.qmd --no-browser. Trace how the preview web server reports /wrong/path/to/image.png as a 404, then make the render behavior report missing resources consistently and verify both command outputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.