jspdf install fails due to github branch referenced as dependency
See original GitHub issueThe dependency file-saver is currently added as a direct reference to a Github branch. This causes errors during install in some cases and during CI/CD.
when installed, package.json in node-modules shows
"file-saver": "github:eligrey/FileSaver.js#1.3.8",
instead of
"file-saver": "2.0.1",
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
jspdf install fails due to github branch referenced as dependency
The dependency file-saver is currently added as a direct reference to a Github branch. This causes errors during install in some cases and ......
Read more >Not find · Issue #2839 · parallax/jsPDF - GitHub
A quick workaround to hide the error for now: My project uses create-react-app under the hood so I have to use a config-overrides.js...
Read more >FileSaver dependency is causing npm install failure #2490
this dependency is causing failure when i try to npm install "file-saver": "github:eligrey/FileSaver.js#1.3.8" in versions 1.5.2 and below, ...
Read more >jsPDF 2.0.0 - Critical dependency: the request of a ... - GitHub
My current issue is trying to make a PDF from HTML, and I'm getting errors from dompurify / html2canvas (tried both with HTML...
Read more >jspdf not installing. · Issue #2572 - GitHub
I have solved the issue by running the npm install in the Git. All reactions.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same problem here. We are all waiting on a release of v1.5.4 Could you pleas let us know what time the release of 1.5.4 will be at?
This is already done in master with #2333, originally reported here #2208 We are all waiting on a release of v1.5.4 since then but yet still nothing.