# The nfuse NPM-helper can't handle updated NPM-packages **URL:** \ **Category:** Bug Reports\ **Created:** [September 22, 2016, 8:46am UTC](https://forums.fusetools.com/t/the-nfuse-npm-helper-cant-handle-updated-npm-packages/2260 "2016-09-22T08:46:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sebastian](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/sebastian/32/594_2.png) [@sebastian](https://forums.fusetools.com/u/sebastian)\ **Post date:** [September 22, 2016, 8:46am UTC](https://forums.fusetools.com/t/the-nfuse-npm-helper-cant-handle-updated-npm-packages/2260/1 "2016-09-22T08:46:57Z")
fuse 0.25.1 nfuse I have a bug report for `nfuse`. The internal requires in a package can get messed up if one does an `npm update` without also removing `NPM-Packages` and (possibly) `build`. Steps to reproduce: 1 Download and unpack the project I am supplying 2 Run the project: ```auto $ npm install $ nfuse $ fuse preview // Fails when running ``` 3 Change version of isomorphic-date in package.json to 0.1.2 4 Update and rerun: ```auto $ npm update isomorphic-date $ uno clean $ fuse preview // Fails again ``` 5 Now remove the generated directories and retry ```auto $ rm -r NPM-Packages $ rm -r build $ nfuse $ fuse preview // Success, the console outputs todays date ``` So I suggest that nfuse removes `NPM-Packages` when a version update is detected and possibly also removes the `build` directory - [Attached ZIP file](https://s3.us-east-2.amazonaws.com/fuse-legacy-forum-assets/g3zxC2P9L8q5-image-1474533994517.zip) ---
**Author:** ![Andreas\_Ronning](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/andreas_ronning/32/303_2.png) [@Andreas\_Ronning](https://forums.fusetools.com/u/Andreas_Ronning)\ **Post date:** [October 26, 2016, 5:31am UTC](https://forums.fusetools.com/t/the-nfuse-npm-helper-cant-handle-updated-npm-packages/2260/2 "2016-10-26T05:31:45Z")
Hey! So nfuse is actually not maintained by fuse as a whole, but rather my own personal project. The best thing you can do when you encounter problems with nfuse is to add issues to that project’s issue tracker: [https://github.com/Sunjammer/nfuse/issues](https://github.com/Sunjammer/nfuse/issues) As for your problem, the quickest way to fix it right now is to run nfuse with the -f flag which forces a complete rebuild.