Skip to content

build(deps): bump jspdf and jspdf-autotable #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

build(deps): bump jspdf and jspdf-autotable #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
105 changes: 47 additions & 58 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,8 @@
"file-saver": "^2.0.5",
"firebase": "^11.9.1",
"framer-motion": "^12.19.1",
Copy link

@sentry sentry bot Jan 5, 2026

Choose a reason for hiding this comment

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

Bug: The default import for jsPDF in TranscriptionResult.tsx is incompatible with the newly upgraded v4.0.0, causing a runtime error on PDF download.
Severity: CRITICAL | Confidence: High

🔍 Detailed Analysis

The upgrade to jspdf v4.0.0 requires a named import (import { jsPDF } from "jspdf";), but the file src/components/transcription/TranscriptionResult.tsx continues to use a default import (import jsPDF from "jspdf";). This will cause a runtime error, such as jsPDF is not a constructor, when a user attempts to use the "Download as PDF" functionality. This action triggers the handleDownloadPdf function, which relies on the incorrect import, causing the feature to fail in production.

💡 Suggested Fix

In src/components/transcription/TranscriptionResult.tsx, change the import statement from import jsPDF from "jspdf"; to import { jsPDF } from "jspdf"; to align with the breaking changes in jspdf v4.0.0.

🤖 Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L38

Potential issue: The upgrade to `jspdf` v4.0.0 requires a named import (`import { jsPDF
} from "jspdf";`), but the file `src/components/transcription/TranscriptionResult.tsx`
continues to use a default import (`import jsPDF from "jspdf";`). This will cause a
runtime error, such as `jsPDF is not a constructor`, when a user attempts to use the
"Download as PDF" functionality. This action triggers the `handleDownloadPdf` function,
which relies on the incorrect import, causing the feature to fail in production.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8182364

"jspdf": "^3.0.1",
"jspdf-autotable": "^5.0.2",
"jspdf": "^4.0.0",
"jspdf-autotable": "^5.0.7",
"jszip": "^3.10.1",
"lucide-react": "^0.523.0",
"marked": "^15.0.12",
Expand Down