Skip to content

Conversation

@erseco
Copy link

@erseco erseco commented Jan 26, 2026

No description provided.

@github-actions
Copy link

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://exelearning.pages.dev/pr-preview/pr-28/

Built to branch gh-pages at 2026-01-26 14:37 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f034b86446

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +84 to +88
const mermaidPath = path.join(process.cwd(), 'public/app/common/mermaid/mermaid.min.js');

if (!fs.existsSync(mermaidPath)) {
throw new Error(`Mermaid script not found at: ${mermaidPath}`);
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Resolve mermaid script relative to package, not cwd

The new loader builds the mermaid path from process.cwd() (lines 84–88), which only works when the CLI is invoked from the repo root. If a user runs elp:export from another working directory (common for CLI use or packaged installs), public/app/common/mermaid/mermaid.min.js won’t exist, initialization fails, and preRenderMermaid falls back to mermaidRendered: false; exports then omit the Mermaid runtime entirely (see the export constants noting Mermaid is never bundled), leaving diagrams unrendered in output. Consider resolving the script path relative to the module/package root (e.g., via import.meta.url/__dirname) or routing through the resource provider used elsewhere.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants