ember-cli-materialize broke my project on Windows?

A warning would have been nice... I've been trying to install ember-cli-materialize, but it fails because, apparently, fsfetch, which seems to be a required optional file, isn't available for the Windows 64 operating system.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'D:\Dev\Projects\catproj\node_modules\node-sass\package.json'

I haven't found the magic incantation to undo this mess. Trying to run "ember server" with it installed or not... ember server

ENOENT: no such file or directory, scandir 'D:\Dev\Projects\catproj\node_modules\broccoli-sass-source-maps\node_modules\node-sass\vendor'
Error: ENOENT: no such file or directory, scandir 'D:\Dev\Projects\catproj\node_modules\broccoli-sass-source-maps\node_modules\node-sass\vendor'
    at Error (native)
    at Object.fs.readdirSync (fs.js:952:18)

It's probably obvious that I did not delete that missing file. Uninstalling the modules isn't sufficient, but hacking up package.json did allow me to resume development. So...

1. How do I rescan for dependencies and simplify package.json?
2. What magic is required that I was missing for materialize on Windows?

Thanks