feat(lua): When possible, use Quarto Lua API from Quarto 1.5.32+ to g…

…et the path to quarto (#51)

Co-authored-by: Barret Schloerke <[email protected]>

.github/workflows/deploy.yml

@@ -4,7 +4,6 @@ on:
   push:
     branches: [main]
   pull_request:
-    branches: [main]
 
 jobs:
   build:

_extensions/quarto-ext/shinylive/_extension.yml

@@ -1,8 +1,8 @@
 name: shinylive
 title: Embedded Shinylive applications
 author: Winston Chang
-version: 0.1.0
-quarto-required: ">=1.2.198"
+version: 0.2.0
+quarto-required: ">= 1.2.198"
 contributes:
   filters:
     - shinylive.lua

_extensions/quarto-ext/shinylive/shinylive.lua

@@ -393,6 +393,16 @@ function getShinyliveBaseDeps(language)
   return deps
 end
 
+-- Legacy quarto cli location
+quarto_cli_path = "quarto"
+if quarto.config ~= nil and quarto.config.cli_path ~= nil then
+  -- * 2024/05/03 - Christophe:
+  --   `quarto run` needs to be called using the same quarto CLI that called the extension.
+  --   This is done by using `quarto.config.cli_path()` from Quarto 1.5 Lua API.
+  --   https://github.com/quarto-dev/quarto-cli/pull/9576
+  quarto_cli_path = quarto.config.cli_path()
+end
+
 return {
   {
     CodeBlock = function(el)
@@ -415,7 +425,7 @@ return {
 
       -- Convert code block to JSON string in the same format as app.json.
       local parsedCodeblockJson = pandoc.pipe(
-        "quarto",
+        quarto_cli_path,
         { "run", codeblockScript, language },
         el.text
       )