## 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.

```text
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'.