NWJS Uncaught Error: Cannot find module 'mdns' - node.js

I have not so much experience with nwjs. If I open my nwjs.app I found this error:
Uncaught Error: Cannot find module 'mdns'
I try to fix it removing node modules and reinstall npm but it doesn't work. I tried to remove mdns module and reinstall but nothing.
I tried to change permission to the folders but it doesn't work too.
I don't found causes and how to fix it.
Thanks in advance for help.

Related

Error "Module not found" while create-react-app and npm start

I am trying to run create-react-app and after entering npm start I am getting this error
Failed to compile.
Module not found: Error: Can't resolve 'C:\Users\sande\OneDrive\Desktop\project#1\client\my-app\node_modules\webpack-dev-server\client\index.js?protocol=ws%3A&hostname=0.0.0.0&port=3000&pathname=%2Fws&logging=none&reconnect=10' in 'C:\Users\sande\OneDrive\Desktop\project#1\client\my-app'
ERROR in Module not found: Error: Can't resolve 'C:\Users\sande\OneDrive\Desktop\project#1\client\my-app\node_modules\webpack-dev-server\client\index.js?protocol=ws%3A&hostname=0.0.0.0&port=3000&pathname=%2Fws&logging=none&reconnect=10' in 'C:\Users\sande\OneDrive\Desktop\project#1\client\my-app'
webpack compiled with 1 error
There is a problem while reading the directory because there is a # character in your file path. Do not use # and similar signs in your directory path. Good work.
I had the same error, I change my path and remove all # form it.
It should be like this #React/myProject/project#1 => React/myProject/project1
Thanks for the help everyone, it resolved the error.

Babel error caused by reference to "process"

I've found myself in a strange predicament—after a recent upgrade to my local app dependencies, the application breaks whenever I make reference to the node process object. Specifically it throws the following errors:
Babel Error: Cannot find module '#babel/plugin-proposal-logical-assignment-operators'
So far, I've tried to resolve this issue with a yarn add of the missing dependency, without success. Could anyone shed light on the issue at hand, or how I might be able to resolve it?
Thanks for your consideration.
I resolved this issue by deleting node_modules and running yarn install.

angular project npm modules randomly deleted

I have the weirdest problem I've ever seen with npm where in the middle of running an angular ng serve, packages from both node and for angular will randomly go missing. In the middle of a save, the project will suddenly not recompile, and will complain about a missing module. Each time it has been different but so far I have had:
Error: ENOENT: no such file or directory, open '.../node_modules/core-js/internals/hidden-keys.js'
Module not found: Error: Can't resolve '../internals/is-pure' in '/.../node_modules/#angular-devkit/build-angular/node_modules/core-js/internals'
An unhandled exception occurred: Cannot find module './internal/streams/stream
An unhandled exception occurred: Cannot find module '/.../node_modules/minipass-collect/node_modules/minipass/index.js'.
Please verify that the package.json has a valid "main" entry
These have just been errors from the last few days, but issues like this has been happening all. to the point where I need to delete node_modules and reinstall everything via npm at least once a day. I'm thinking the error has more to do with node or NPM than with my Angular set up, as some of these missing packages appear to be node core packages.
I've already tried reinstalling npm globally via npm install -g npm and it hasn't helped anything. I'm afraid that I'm going to have to just reinstall node completely.
Any help would be appreciated, thank you.
EDIT: upon further debugging, I'm noticing that the modules missing are always from #angular-devkit/build-angular/node_modules/core-js/modules. In addition to losing random modules like 'is-pure', the app will also randomly recompile many times when running ng serve
I figured out what was going on, if anyone in the future has the same problem. Turns out the answer has nothing to do with me botching my npm config. I didn't realize that on new Macbooks, any directory in the desktop is automatically managed by iCloud. At some point, probably an older version of the code before I migrated to Angular 9 was syncing the old code into my project. I was able to resolve this issue by changing the name of the parent directory where my project lived from filename to filename.nosync. adding '.nosync' causes iCloud to ignore syncing for whatever is in that file. I know I should have caught this, but hopefully this will help any mac users in the future who are experiencing similar problems.

'node-jose' library is using 'zlib' library as a dependency which throws an error. How do I fix it and have you encountered the same problem?

I'm trying to use the node-jose library with angular7 for the use with JWEs. The library uses zlib as a dependency and it throws an error when compiling:
ERROR in ./node_modules/zlib/lib/zlib.js
Module not found: Error: Can't resolve './zlib_bindings' in '~\WebApp\node_modules\zlib\lib'
I opened the 'zlib.js' file and the contents are the following:
module.exports = require('./zlib_bindings');
The problem is that the required file doesn't exist. I inspected the rest of the library and there is no such file in the whole library.
I searched the whole internet and no one has described the same problem as I have. There are some discussions regarding the 'node-jose' library but none of those issues are related to 'zlib'.
I would be extremely thankful if only someone would say they share the same error. Thanks in advance!
I found the answer.
Angular isn't showing an error when compiling but shows an error in the browser. It's because the browser doesn't have 'node' libraries integrated so it can't start the 'zlib' library. Installing the 'zlib' library in 'node_modules' doesn't help since it's deprecated.
Using the 'browserify-zlib' library and changing the ...require('browserify-zlib') in all my dependencies has fixed the issue.
This PR will fix the issue in node-jose
https://github.com/cisco/node-jose/pull/264
This is published to npm as node-jose-browserify, https://www.npmjs.com/package/node-jose-browserify
npm i node-jose-browserify

Trouble with grunt

I am a first time user of node and grunt and npm and express and all that jazz, trying to get things setup and everything up to this point has been smooth. I have grunt installed globally. I try to run it in my project directory and I get the following error:
Running "sass:dist" (sass) task
grunt: symbol lookup error:
/home/tyler/foo/learningNode/new-proj/new-proj/node_modules/grunt-sass/node_modules/node-sass/bin/linux-x64-v8-3.22/binding.node:
undefined symbol:
_ZN4node12MakeCallbackEN2v86HandleINS0_6ObjectEEENS1_INS0_8FunctionEEEiPNS1_INS0_5ValueEEE
I've tried looking this up all over and can't even find the phrase "grunt: symbol lookup error:" anywhere. Seriously at a complete loss. If anyone has a clue it would be greatly appreciated.
Sorry, forgot to mention I am using Ubuntu 12.04.
If you're using node 0.11 the node-sass module doesn't work, not sure if that's the issue you're running into but there's an issue open on it here https://github.com/andrew/node-sass/issues/229

Resources