May an npm update cause malfunciton or breakdown?

I've a trouble with the frontend part of an application. Code build correctly in our local machines. In production build is broken (gulp build fails). npm and node versions are different locally and remotely.

Local versions:

prompt> npm -v
3.10.8
prompt> node -v
v6.9.1

Remote versions:

prompt> npm -v
3.9.5
prompt> node -v
v6.2.2

Actually build fails due to strange reason. Strange just because all works fine locall.

warning Error: ENOENT: no such file or directory, open '/home/user/admin.example.com/.tmp/serve/styles/kendo.common.min.css.map'
warning at Error (native)
warning at Object.fs.openSync (fs.js:634:18)
warning at Object.fs.readFileSync (fs.js:502:33)
warning at fromSource (/home/user/admin.example.com/node_modules/clean-css/lib/utils/input-source-map-tracker.js:84:30)
warning at InputSourceMapStore.track (/home/user/admin.example.com/node_modules/clean-css/lib/utils/input-source-map-tracker.js:237:5)
warning at Object.whenDone (/home/user/admin.example.com/node_modules/clean-css/lib/clean.js:145:44)
warning at processNext (/home/user/admin.example.com/node_modules/clean-css/lib/imports/inliner.js:105:13)
warning at importFrom (/home/forge/admin.example.com/node_modules/clean-css/lib/imports/inliner.js:79:10)
warning at ImportInliner.process (/home/forge/admin.example.com/node_modules/clean-css/lib/imports/inliner.js:38:10)
warning at /home/forge/admin.example.com/node_modules/clean-css/lib/clean.js:120:41
warning at _combinedTickCallback (internal/process/next_tick.js:67:7)
warning at process._tickCallback (internal/process/next_tick.js:98:9)
execute gulp build

via sensorario