Node: Cannot find module "mongoose" / Cannot install mongoose correctly -

-

wenn try start javascript-file test connection mongodb error message mongoose module cannot find. have installed mongoose "npm install mongoose" in node.js directory. when install mongoose following messages, thin not installed correctly:

> kerberos@0.0.10 install c:\zimmermann\nodejs\node_modules\mongoose\node_module s\mongodb\node_modules\mongodb-core\node_modules\kerberos > (node-gyp rebuild 2> builderror.log) || (exit 0)  c:\zimmermann\nodejs\node_modules\mongoose\node_modules\mongodb\node_modules\mon godb-core\node_modules\kerberos>if not defined npm_config_node_gyp (node "c:\zim mermann\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bi n\node-gyp.js" rebuild )  else (rebuild)  > bson@0.2.21 install c:\zimmermann\nodejs\node_modules\mongoose\node_modules\mo ngodb\node_modules\mongodb-core\node_modules\bson > (node-gyp rebuild 2> builderror.log) || (exit 0)   c:\zimmermann\nodejs\node_modules\mongoose\node_modules\mongodb\node_modules\mon godb-core\node_modules\bson>if not defined npm_config_node_gyp (node "c:\zimmerm ann\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\no de-gyp.js" rebuild )  else (rebuild) mongoose@4.0.1 node_modules\mongoose ├── regexp-clone@0.0.1 ├── sliced@0.0.5 ├── hooks-fixed@1.0.1 ├── mpromise@0.5.4 ├── muri@1.0.0 ├── mpath@0.1.1 ├── async@0.9.0 ├── kareem@1.0.0 ├── ms@0.1.0 ├── mquery@1.4.0 (debug@0.7.4, bluebird@2.3.2) └── mongodb@2.0.24 (readable-stream@1.0.31, mongodb-core@1.1.20)

what can mongoose works correctly? have idea?

best regards benny

you can either of 2 things make run :-

1) install mongoose globally below steps :-

a)npm install mongoose -g

b) go app directory, module.js located , run

npm link mongoose

explanation :- when install package globally via npm, downloaded global node_module folder. me(mac user), it's under /usr/local/lib/node_modules/mongoose. link directory trying run node.js.

2) another approach install mongoose locally, not globally via

npm install mongoose

after following either of these, seeing node_modules --> mongoose folder under 'node.js' directory, means mongoose has been installed.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more