Hi, I'm creating a chrome extension and I got this error when I tried to import the library

Uncaught ReferenceError: js_file_downloader__WEBPACK_IMPORTED_MODULE_0__ is not defined

I'm tried to import using jsFileDownloader, JsFileDownloader and with curly braces but it didn't worked. How can I fix this?

It is useful to always reject a promise with an Error (superclass of downloadException). Using an Error ensures you have access to stack traces which can help with debugging: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/reject#description

In our case, using an Error as the reject reason would help give Sentry better error information: https://github.com/getsentry/sentry-javascript/issues/2546#issuecomment-645357265

Hi, I want to ask is there any support for sending cookies with the request just like we can do with the JS Fetch by adding credentials: 'include' or with the XMLHttpRequest just by adding request.withCredentials = true;.

Kindly can anyone help me with this?

When trying to use it in a Cordova-electron app I get this error: Uncaught (in promise) TypeError: Failed to execute 'createObjectURL' on 'URL': Overload resolution failed. at t. (js-file-downloader.min.js:10)

(does not depend on the file type or server).

I don't see any way to get the status code from the error message thrown. Use case = 401 (Unauthorized) refresh users token and try again.

Looking a bit more into it the exceptions just might not be working correctly, the lib attempts to use -

https://github.com/AleeeKoi/js-file-downloader/blob/master/src/exception.js

Which then throws -

Error: Downloader error: TypeError: Cannot set property 'message' of undefined at XMLHttpRequest.request.onload (js-file-downloader.js:217)

Which prevents the error message from properly getting emitted out.

I need to download multiple files and show the status of eatch downloaded file... So i create for loop. Is there any way to add to information into process function about file status HTML element?

thanks

Hi. There is a small typo in the current type definition of headers. Written this way it allow only 1 header : headers?: [{ name: string, value: string }];

To allow multiple headers, the correct syntax is headers?: { name: string, value: string }[]

(or it could be Array<{ name: string, value: string }>)

Hey, I was wondering if you ever thought about appending the filename with the correct ending (e.g .pdf) following the mime type returned from the server. I implemented something like that with js-file-download but this package doesn't have type declarations.

Here a snippet:

axios
  .get(url, {
    responseType: 'blob',
  })
  .then((response) => response.data)
  .then((blob) => {
    // fileDownload is the function of the js-file-download library
    // It accepts the following: 
    // data: string | ArrayBuffer | ArrayBufferView | Blob,
    // filename: string,
    // mime?: string,
    // bom?: string
    fileDownload(blob, generateFilename(filename), blob.type);
  })
  .catch((error) => {
    console.error(error);
    throw error;
  });

The library does support a custom mime and what I did is just using the one which the blob reflects. Would be cool to have some ability to turn this on automatically.

What are your thoughts? Let me know 😉

Hello! Trying to get file, but i need to make a POST request with params. A pdf file will be generated with params, that must be send in post request, like name and so on.

new JsFileDownloader({
        url: process.env.REACT_APP_API_URL + url,
        headers: [{ name: "authorization", value: `Bearer ${token}` }],
        method: "POST",
        withCredentials: true,
        filename: "NDA.pdf",
        contentType: "application/json;charset=UTF-8",
      }) //@ts-ignore
        .catch(function (error) {
          console.dir("download error", error);
         
        });

Can you add a body field for POST request ?

request.setRequestHeader('Content-type', 'application/x-www-form-urlencoded');

sets a content-type for every request, even for GET requests where there is no Body, and thus no content-type. https://stackoverflow.com/questions/5661596/do-i-need-a-content-type-header-for-http-get-requests

This causes issues for some REST-Frameworks and Firewalls, complaining about content-type being set without body.

There is a parameter mobileDisabled but it's not used anywhere in the code. Or did I miss something?

The code and doc would probably require clarification in regards to that parameter and forceDesktopMode, to clearly explain how to make it work on mobile.

For instance the doc mentions that mobileDisableddefaults to false, while it's true in the code. But anyhow this parameter is not used.

Hello and thanks for this great library.

I'm having issues with a specific file, with is a large video (3.1GB), and stored on Amazon S3. It seems that the file is being downloaded, I can see the progress through the process callback. Once the downloading is complete, the file is saved, but instead of the expected video file, there is a 4 bytes file, which is just a text file containing the string "null".

Any ideas?

Thanks, Tom

I am using the latest version of this package minified for an internal project of the company I work and I noticed that when using HTTPS and trying to download files in different formats it throws an error on the console. But this only happens on the first try, on the next's one the download proceeds correctly and no errors are shown. Our source code that this happen is something like this I enabled the nativeFallbackOnError to true and the error was So I tried debugging this function and also the endpoint and it seems that after returning the file to download it cannot be read and the error.request.response is null and the responseText is filled with [Exception: DOMException: Failed to read the 'responseText' property from 'XMLHttpRequest': The value is only accessible if the object's 'responseType' is '' or 'text' (was 'arraybuffer').

For whatever reason, this does not appear to work on chrome mobile on iOS. It seems to download, but nothing ends up in our files. I believe this used to work so possibly something changed on chrome. It works on safari. This is how we call the JsFileDownloader:

new JsFileDownloader({
    forceDesktopMode: true,
    withCredentials: true,
    nativeFallbackOnError: true,
    headers: [
      {
        name: "timezoneOffset",
        value: new Date().getTimezoneOffset().toString(),
      },
    ],
    url: process.env.REACT_APP_API_URL + `${endpoint}?${stringify(params)}`,