quarto-dev / quarto-dev/quarto

Shiny server does not allow local OJS/js module imports

Open
#653 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Problem:
When trying to import a local module for OJS as outlined here when server: shiny, an error occurs and the module cannot be used. The module is found, otherwise the error will occur on initial build and the render will fail, but it is unable to be imported. This does not happen if the shiny server is not used. It would be useful to be able to store OJS code (such as functions that can make plots) as a .qmd module and import it into a quarto document running with a shiny server to feed in the data.

Currently this is the error that occurs:
Error: error loading dynamically imported module Loading module from “http://localhost:6366/square.js” was blocked because of a disallowed MIME type (“text/html”)

Minimal Example:

square.js:
export function square(x) { return x * x; }

This works:

---
title: "Module Import Test"
format: html
---

```{ojs}
//| echo: true
//| output: true

import { square } from "./square.js";
square(5);
```

This does not:

---
title: "Module Import Test"
format: html
server: shiny

---

```{ojs}
//| echo: true
//| output: true

import { square } from "./square.js" // This recieves an error and square is undefined. 
square(x) 
```

```{ojs}
x * x  // This code is able to run perfectly fine
```

```{r}
#| context: server
#| echo: true
x <- reactive(5)

ojs_define(x)
```

Environment Information
Quarto Version: 1.7.6
Browser: Firefox & Chrome
Shiny Version: 1.10.0
R Version: 4.4.2

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the failure with square.js and the minimal Quarto document using server: shiny, comparing it with the working non-Shiny document. Start by tracing how the local JavaScript module is served during Shiny rendering; done means the local OJS import loads and square(5) works in the Shiny document without the MIME-type error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.