Hy ..
I have installed Meteor successful on Windows XP. Creating a new project works, but running the project doesn't work. Application crashes with following error:
module.js:485
process.dlopen(filename, module.exports);
^
Error: no errorC:\Programme\Meteor\lib\node_modules\fibers\bin\win32-ia32\fibers.node
at Object.Module._extensions..node (module.js:485:11)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object.<anonymous> (C:\Programme\Meteor\lib\node_modules\fibers\fibers.js:13:1)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
Exited with code: 1
Your application is crashing. Waiting for file change.
Environment:
Windows XP (SP3)
node.js v0.8.3
meteor v0.3.7
npm v1.1.43
I'm very thankful for every tip.
I had the exact same problem, but on Windows 8 Release Preview. It seems the fibers package shipped with Meteor 0.3.7 does not work properly. Here's what worked for me:
First, I opened a command prompt with administrator rights and navigated to:
C:\Program Files\Meteor\lib
Or in your case:
C:\Programme\Meteor\lib
And then just reinstalled fibers:
npm remove fibers
npm install fibers
Let me know if that works for you.
Related
react-native -v gives me this:
react-native-cli: 2.0.1
react-native: 0.57.1
When I run any other command like react-native info or react-native run-android keep giving me below error:
function getCliConfig(){var cliArgs,config,expoAssetPluginPath;return regeneratorRuntime.async(function getCliConfig$(_context){while(1){switch(_context.prev=_context.next){case 0:
^
ReferenceError: regeneratorRuntime is not defined
at getCliConfig (/Applications/MAMP/htdocs/juices/node_modules/react-native/local-cli/core/index.js:128:64)
at Object.<anonymous> (/Applications/MAMP/htdocs/juices/node_modules/react-native/local-cli/core/index.js:181:30)
at Module._compile (internal/modules/cjs/loader.js:654:30)
at Module._compile (/Applications/MAMP/htdocs/juices/node_modules/pirates/lib/index.js:83:24)
at Module._extensions..js (internal/modules/cjs/loader.js:665:10)
at Object.newLoader [as .js] (/Applications/MAMP/htdocs/juices/node_modules/pirates/lib/index.js:88:7)
at Module.load (internal/modules/cjs/loader.js:566:32)
at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
at Function.Module._load (internal/modules/cjs/loader.js:498:3)
at Module.require (internal/modules/cjs/loader.js:598:17)
Actually this issue related to react-native version, For now, Expo supporting till version 0.55.4. Please downgrade react-native version and try again and I hope it will work.
Expo Documentation (Supported Versions):-
https://docs.expo.io/versions/latest/sdk/#sdk-version
Try this for downgrade your react-native version:-
npm install react-native#0.55.4
I'm on MacOS and installed the Heroku CLI a few months ago and ran into this error trying to use the command line tools today:
Error: Cannot find module '{user profile}/.local/share/heroku/client/6.15.25-635e5c6/package.json'
at Function.Module._resolveFilename (module.js:555:15)
at Function.Module._load (module.js:482:25)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at run ({user profile}/.local/share/heroku/client/6.15.25-635e5c6/node_modules/#cli-engine/engine/lib/cli.js:82:22)
at Object.<anonymous> ({user profile}/.local/share/heroku/client/6.15.25-635e5c6/bin/heroku.js:7:1)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
I tried brew uninstall heroku/brew/heroku and then reinstalling with no change in the error.
I found this issue on GitHub that fixed it.
The fix is just delete ~/.local/share/heroku/client and it worked fine again as normal.
Hi I am trying to install zmq module on a linux machine.Below are the steps that i followed
• Make sure you have the following packages installed (sudo apt-get install binutils libtool autoconf automake)
• Get the latest POSIX tarball (http://zeromq.org/intro:get-the-software) and untar it
• Run configure (./configure)
• Run make (sudo make install)
• npm install zmq or npm update if you already have it listed in your package.json
• sudo ldconfig (otherwise you might get the error "connot open shared object file")
But when i ran the above steps i got the error as below
Error: libzmq.so.3: cannot open shared object file: No such file or directory
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/var/MLIDeployment/MLI/zeromq-4.0.3/node_modules/zmq/lib/index.js:8:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
I'm stuck here any help regarding this will be much helpful
The error you are getting is that libzmq.so cannot not found.
You need to add the install directory (defaults to /usr/local/lib) to LD_PATH.
To add it you need to execute:
sudo echo "/usr/local/lib" >> /etc/ld.so.conf.d/local-lib.conf
sudo ldconfig
Hope this works.
I have installed node.js v0.8.8 both from the pkg installer and compiled from source. Yet I get the following error when trying to run npm. Any help would be appreciated.
> $ npm --help
>
> /usr/lib/node_modules/npm/lib/utils/config-defs.js:5 , stdio =
> process.binding("stdio")
> ^ Error: No such module
> at Object.<anonymous> (/usr/lib/node_modules/npm/lib/utils/config-defs.js:5:21)
> at Module._compile (module.js:449:26)
> at Object.Module._extensions..js (module.js:467:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:362:17)
> at require (module.js:378:17)
> at Object.<anonymous> (/usr/lib/node_modules/npm/lib/utils/ini.js:43:18)
> at Module._compile (module.js:449:26)
> at Object.Module._extensions..js (module.js:467:10)
I had the exact same issue upgrading from Node.JS 0.4 to 0.8. What worked for me was the following:
The OSX Node.JS package installer erroneously does not remove the old 0.4 npm installation in /usr/bin, which then conflicts with the new 0.8 one in /usr/local/bin. It just overwrites whatever is there already. I nuked the old one by deleting it, but to make sure, I decided a clean install would be better:
curl https://npmjs.org/install.sh | sudo clean=yes sh
There was one last problem: after the install, even though a which npm correctly returns /usr/local/bin/npm, bash kept trying to execute from /usr/bin. This is because on OSX, bash has hashed the executable name. The hashing saves repeated searches of all directories in your PATH every time you execute common programs. A hash -r at the command line took care of this issue.
You are most likely using an old NPM version somehow.
see: npm issue
I'm working to get node running on a new mac. I downloaded the installed at http://nodejs.org/
I then git cloned my node repo, ran npm install and npm update, and then node web.js which then errors with:
$ node web.js
Error: Cannot find module '/Users/me/Sites/mysite-node/node_modules/pg/lib/native/../../build/default/binding'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object.<anonymous> (/Users/me/Sites/mysite-node/node_modules/pg/lib/native/index.js:12:12)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
I'm new to node, any ideas or suggestions on where to look? Thanks
You need to install the postgresql libraries on your machine. For example under Fedora you'd:
yum install postgresql.x86_64
yum install postgresql-server.x86_64
If you already had pg install you'd need to rebuild it:
npm rebuild pg
Then to verify everything is working at the terminal type:
node
Then in the node REPL type:
var pg = require('pg').native
And you shouldn't get an error
The Error shows that npm installation of the pg module has not built the native bindings properly. Modify your code as follows:
//var pg = require('pg').native;
var pg = require('pg');