quarto-dev / quarto-dev/quarto-cli

Live Quarto extension handled differently by Positron/VS Code vs RStudio

Open
#13,077 6 comments 0 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Jul 15, 2025.

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

Description

Bug description

Hi,

Both VS Code and Positron handle the live Quarto extension differently from RStudio.

Steps to reproduce
  1. Create a book project my_book.
  2. Install quarto-live in the root folder: quarto add r-wasm/quarto-live.
  3. Create another folder, say chapter_01
  4. In chapter_01 create chapter_01.qmd.
  • Populate the file with
---
title: "Chapter-01"
format: live-html
engine: knitr
webr:
  packages:
    - tidyverse
    - infer
    - insight
---

{{< include ../_extensions/r-wasm/live/_knitr.qmd >}}

```{webr}
# Testing


```
  1. Add - chapter_01/chapter_01.qmd to chapter: in _quarto.yml.

Just for reference:

Image

If you render this project using VS Code or Positron, it will not work properly.

If you render using RStudio it will.

Actual behavior
  • Rendering using VS Code:
Image
Expected behavior
  • Rendering using RStudio:
Image
Your environment
Quarto: 1.7.32
Positron:

Positron Version: 2025.07.0 build 204
Code - OSS Version: 1.100.3
Commit: 03ae7a5393c776bb24c23d2aa6a6bfbba90cbc5e
Date: 2025-06-30T16:29:03.492Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Rstudio:

RStudio 2025.05.1+513 "Mariposa Orchid" Release (ab7c1bc795c7dcff8f26215b832a3649a19fc16c, 2025-05-30) for macOS
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) RStudio/2025.05.1+513 Chrome/132.0.6834.210 Electron/34.5.1 Safari/537.36, Quarto 1.7.32 (/Applications/quarto/bin/quarto)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.