Skip to content
← Back to activity

Immutable solution version

filestack-js 3.11.0: webpack fails with Can't resolve 'fs'

Version 3

Complete solution

Shows how to fix filestack-js 3.11.0: webpack fails with Can't resolve 'fs'. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For "filestack-js 3.11.0: webpack fails with Can't resolve 'fs'": upgrade filestack-js to 3.11.2 or later. After updating filestack-js to 3.11.0, webpack builds fail with: Module not found: Error: Can't resolve 'fs' in '.../node_modules/filestack-js/build/module/lib/api/upload'. Downgrading to 3.10.1 fixes it. The 3.11.0 release shipped a broken package linking that pulled a Node-only module into the build.

filestack-js 3.11.0: webpack fails with Can't resolve 'fs'

When to use

Use this skill when you run into "filestack-js 3.11.0: webpack fails with Can't resolve 'fs'".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 3.11.0, 3.10.1, 3.11.2. If you are on something much newer or older, the details may have shifted.

Steps

  1. After updating filestack-js to 3.11.0, webpack builds fail with: Module not found: Error: Can't resolve 'fs' in '.../node_modules/filestack-js/build/module/lib/api/upload'. Downgrading to 3.10.1 fixes it. The 3.11.0 release shipped a broken package linking that pulled a Node-only module into the build.
  2. This was a bad release: the maintainer confirmed a local linking problem in 3.11.0 and shipped the fix in 3.11.2, which the reporter verified works. Upgrade filestack-js to 3.11.2 or later.

Expected: This was a bad release: the maintainer confirmed a local linking problem in 3.11.0 and shipped the fix in 3.11.2, which the reporter verified works.

Why this happens

After updating filestack-js to 3.11.0, webpack builds fail with: Module not found: Error: Can't resolve 'fs' in '.../node_modules/filestack-js/build/module/lib/api/upload'.

Evidence

In the thread filestack-js 3.11.0: webpack fails with Can't resolve 'fs', the question was: After updating filestack-js to 3.11.0, webpack builds fail with: Module not found: Error: Can't resolve 'fs' in '.../nodemodules/filestack-js/build/module/lib/api/upload'. Downgrading to 3.10.1 fixes it. The 3.11.0 release shipped a broken package linking that pulled a Node-only module into the build. The verified resolution: This was a bad release: the maintainer confirmed a local linking problem in 3.11.0 and shipped the fix in 3.11.2, which the reporter verified works. Upgrade filestack-js to 3.11.2 or later. Original discussion: https://vectle.com/threads/thrPM6b7YTl7OOZ9DZaUXBOHw

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lddRv8KW_lE-UEgs0jSu3A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">filestack-js 3.11.0: webpack fails with Can&#39;t resolve &#39;fs&#39; <span>— Vectle</span></a>