ASP.NET

Is it enough for methods to be capture and report JavaScript errors on web applications on computer and mobile devices?

window.onerror = function (msg, url, lineNo, columnNo, error) {
	//post data for log
	return true;
};

Public Function Something(val As Integer) As Integer
'Code to run
Return Something
End Function

gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\SourceCode\customerserviceweb\CustomerServiceWeb.Web\node_modules\node-gyp\lib\configure.js:483:19)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\SourceCode\customerserviceweb\CustomerServiceWeb.Web\node_modules\node-gyp\lib\configure.js:508:16)
gyp ERR! stack     at C:\SourceCode\customerserviceweb\CustomerServiceWeb.Web\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:154:21)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\SourceCode\\customerserviceweb\\CustomerServiceWeb.Web\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\SourceCode\customerserviceweb\CustomerServiceWeb.Web\node_modules\node-sass
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.5.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.5.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\e09795\AppData\Roaming\npm-cache\_logs\2019-01-24T21_03_42_886Z-debug.log