Skip to content
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.

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

FileSaver dependency is causing npm install failure #2490

Closed
allenksun opened this issue Jun 7, 2019 · 4 comments
Closed

FileSaver dependency is causing npm install failure #2490

allenksun opened this issue Jun 7, 2019 · 4 comments

Comments

@allenksun
Copy link

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, it's listed with a version number, but now it has this "github:eligrey/FileSaver.js#1.3.8" syntax which appears to be causing it to fail

@hakimio
Copy link

hakimio commented Jun 18, 2019

FileSaver guys deleted the "1.3.8" branch.
As a workaround you can add a resolution to your package.json:

"resolutions": {
    "jspdf/file-saver": "github:eligrey/FileSaver.js#e865e37af9f9947ddcced76b549e27dc45c1cb2e"
  }

@skkallayath
Copy link

There is an npm package for file-saver

Try the following

npm install file-saver --save

And add the following to package.json

"resolutions": {
    "jspdf/file-saver": "file-saver"
  }

@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

eturino added a commit to eturino/material-table that referenced this issue Jan 13, 2021
this is the same as mbrn#2442 which was closed.

## Related Issue

Relate the Github issue with this PR using backstage/backstage#2263

## Description

Simple words to describe the overall goals of the pull request's commits.

## Additional Notes

jspdf fileSaver issue parallax/jsPDF#2490. When the dependency configured to fetch directly from github, this caused an issue while running npm install in isolated environment, and the issue already been patched in jspdf, we just need to do an update here
@mohsin1993
Copy link

try deleting package-lock.json and run npm install again

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

No branches or pull requests

4 participants