[MongoDB] Mongoose module 설치

1. nodejs가 설치된 경로로 이동

 

(1) 경로 확인

Copy path (Ctrl + Shift + C)

 

(2) 경로 이동

PS C:\Program Files\nodejs> cd 'C:\workspace\Study\Hello NodeJS'
PS C:\workspace\Study\Hello NodeJS> dir


    디렉터리: C:\workspace\Study\Hello NodeJS


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----     2020-02-11   오후 3:32                .idea
d-----     2020-02-06   오후 5:33                bin
d-----     2020-02-11  오전 11:32                model
d-----     2020-02-06   오후 4:27                node_modules
d-----     2020-02-06   오후 4:27                public
d-----     2020-02-06   오후 7:00                routes
d-----     2020-02-06   오후 5:59                views
-a----     2020-02-11  오전 11:29           1421 app.js
-a----     2020-02-06   오후 4:27            296 Hello NodeJS.iml
-a----     2020-02-06   오후 4:27          14974 package-lock.json
-a----     2020-02-06   오후 4:27            298 package.json


PS C:\workspace\Study\Hello NodeJS>

 

---

 

2. npm을 이용하여 mongoose 설치

 

(1) 설치 : npm install mongoose --save

PS C:\workspace\Study\Hello NodeJS> npm install mongoose --save
+ mongoose@5.8.11
added 19 packages from 13 contributors and audited 167 packages in 12.307s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities

PS C:\workspace\Study\Hello NodeJS>

 

(2) package.json 확인

{
  "name": "hello-nodejs",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "node ./bin/www"
  },
  "dependencies": {
    "cookie-parser": "~1.4.4",
    "debug": "~2.6.9",
    "ejs": "~2.6.1",
    "express": "~4.16.1",
    "http-errors": "~1.6.3",
    "mongoose": "^5.8.11",
    "morgan": "~1.9.1"
  }
}

 

 

---

 

ETC. 에러 케이스

 

1. 잘못된 경로에 설치할 경우 (nodejs가 설치된 경로가 아닌 package.json이 존재하는 경로에 설치해야함)

PS C:\Program Files\nodejs> npm install mongoose --save
npm WARN enoent ENOENT: no such file or directory, open 'C:\Program Files\nodejs\package.json'
npm WARN nodejs No description
npm WARN nodejs No repository field.
npm WARN nodejs No README data
npm WARN nodejs No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: memory-pager@1.5.0 (node_modules\memory-pager):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sparse-bitfield@3.0.3 (node_modules\sparse-bitfield):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: saslprep@1.0.3 (node_modules\saslprep):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'

npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\Program Files\nodejs\node_modules\.staging
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'
npm ERR!  [OperationalError: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.staging'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'mkdir',
npm ERR!     path: 'C:\\Program Files\\nodejs\\node_modules\\.staging'
npm ERR!   },
npm ERR!   stack: "Error: EPERM: operation not permitted, mkdir 'C:\\Program Files\\nodejs\\node_modules\\.staging'",
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: 'C:\\Program Files\\nodejs\\node_modules\\.staging'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\line play\AppData\Roaming\npm-cache\_logs\2020-02-11T06_10_30_063Z-debug.log
PS C:\Program Files\nodejs>