• using R version 4.4.1 (2024-06-14)
• using platform: aarch64-apple-darwin20
• R was compiled by     Apple clang version 14.0.0 (clang-1400.0.29.202)     GNU Fortran (GCC) 12.2.0
• running under: macOS Ventura 13.4
• using session charset: UTF-8
• checking for file ‘froggeR/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘froggeR’ version ‘0.3.0’
• package encoding: UTF-8
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘froggeR’ can be installed ... [3s/3s] OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... OK
• checking ‘build’ directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [1s/1s] OK
• checking whether the package can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the package can be unloaded cleanly ... [1s/1s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/1s] OK
• checking whether the namespace can be unloaded cleanly ... [1s/1s] OK
• checking loading without being on the library search path ... [1s/1s] OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [2s/2s] OK
• checking Rd files ... [0s/0s] OK
• checking Rd metadata ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [1s/1s] ERROR Running examples in ‘froggeR-Ex.R’ failed The error most likely occurred in: > ### Name: quarto_project > ### Title: Create a Custom 'Quarto' Project > ### Aliases: quarto_project > > ### ** Examples > > if (quarto::quarto_version() >= "1.4") { + # Create a temporary directory for testing + tmp_dir <- tempdir() + + # Create the Quarto project with custom YAML & associated files + quarto_project("frogs", path = tempdir(), custom_yaml = TRUE) + + # Confirms files were created (optional, for user confirmation) + file.exists(file.path(tmp_dir, "frogs.rproj")) # Rproj file + file.exists(file.path(tmp_dir, "frog.qmd")) # Quarto doc + file.exists(file.path(tmp_dir, "_quarto.yml")) # project YAML file + + # Create a new Quarto project with standard Quarto YAML + # quarto_project('frogs_standard', path = tempdir(), custom_yaml = FALSE) + + # Clean up: Remove the created temp directory and all files + unlink(list.files(tempdir(), full.names = TRUE), recursive = TRUE) + } Error in `find_quarto()`: ! Quarto command-line tools path not found! Please make sure you have installed and added Quarto to your PATH or set the QUARTO_PATH environment variable. Backtrace:     ▆  1. └─quarto::quarto_version()  2. └─quarto:::find_quarto()  3. └─cli::cli_abort(quarto_not_found_msg)  4. └─rlang::abort(...) Execution halted
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [2s/2s] OK   Running ‘testthat.R’ [1s/1s]
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [10s/11s] OK
• checking PDF version of manual ... [4s/4s] OK
• DONE Status: 1 ERROR
• using check arguments '--no-clean-on-error '