quarto-dev / quarto-dev/quarto-cli

quarto project render empty if a parent dir is .hidden

Open
#3,186 9 comments 4 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Jun 24, 2026.

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

Description

Bug description

I was confused for a while why my project wasn't rendering anymore with no error without me making any changes to it. The reason turned out to be that I had moved the project to a path that had a directory that starts with a . (hidden).

I realize ignoring hidden directories in the project directory is intended per https://quarto.org/docs/projects/quarto-projects.html#render-targets, but perhaps it was not the intention to ignore everything if a parent directory is hidden? It might seem odd to work under a hidden dir, but in my case it was ~/.julia/dev/, where Julia package development typically takes place.

A simple way to reproduce (this is on Windows):

PS D:\temp\.hidden> quarto create-project myproject
Creating project at D:\temp\.hidden\myproject:
  - Created _quarto.yml
  - Created myproject.qmd
PS D:\temp\.hidden> quarto render myproject
PS D:\temp\.hidden> quarto -v
1.2.262
Checklist
  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.

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.