DEV Community

Edgar Lindo
Edgar Lindo

Posted on

Why am I getting tons of errs when adding mongoose to REACT?

Sure.. I can run npm audit fix --force .. but REACT goes on error after error to the point where it doesn't responds any more..

Is this a mongoose problem? Is there another way to work with it?

Image description

Top comments (3)

Collapse
 
elindo586 profile image
Edgar Lindo

$ npm fund
test@0.1.0
├─┬ opencollective.com/mongoose
│ │ └── mongoose@6.2.0
│ └── github.com/sponsors/feross
│ └── buffer@5.7.1, base64-js@1.5.1, ieee754@1.2.1, run-parallel@1.2.0, queue-microtask@1.2.3, safe-buffer@5.2.1
├─┬ github.com/chalk/chalk?sponsor=1
│ │ └── chalk@4.1.2
│ └── github.com/chalk/ansi-styles?spons...
│ └── ansi-styles@4.3.0, ansi-styles@5.2.0
├── opencollective.com/babel
│ └── @babel/core@7.17.0
├─┬ github.com/sponsors/gregberge
│ │ └── @svgr/webpack@5.5.0, @svgr/core@5.5.0, @svgr/plugin-jsx@5.5.0, @svgr/babel-preset@5.5.0, @svgr/babel-plugin-add-jsx-attribute@5.4.0, @svgr/babel-plugin-remove-jsx-attribute@..., @svgr/babel-plugin-remove-jsx-empty-expr..., @svgr/babel-plugin-replace-jsx-attribute..., @svgr/babel-plugin-svg-dynamic-title@5.4.0, @svgr/babel-plugin-svg-em-dimensions@5.4.0, @svgr/babel-plugin-transform-react-nativ..., @svgr/babel-plugin-transform-svg-compone..., @svgr/hast-util-to-babel-ast@5.5.0, @svgr/plugin-svgo@5.5.0
│ └── opencollective.com/core-js
│ └── core-js-compat@3.21.0, core-js-pure@3.21.0, core-js@3.21.0
├── opencollective.com/browserslist
│ └── browserslist@4.19.1, caniuse-lite@1.0.30001307
├── opencollective.com/webpack
│ └── css-loader@6.6.0, css-minimizer-webpack-plugin@3.4.1, schema-utils@4.0.0, eslint-webpack-plugin@3.1.1, file-loader@6.2.0, mini-css-extract-plugin@2.5.3, postcss-loader@6.2.1, sass-loader@12.4.0, source-map-loader@3.0.1, style-loader@3.3.1, terser-webpack-plugin@5.3.1, webpack@5.68.0, schema-utils@2.7.0, webpack-dev-middleware@5.3.1
├─┬ opencollective.com/eslint
│ │ └── eslint@8.8.0
│ ├── github.com/sponsors/mysticatea
│ │ └── eslint-utils@3.0.0, regexpp@3.2.0
│ └── github.com/sponsors/isaacs
│ └── rimraf@3.0.2, glob@7.2.0
├─┬ opencollective.com/html-webpack-pl...
│ │ └── html-webpack-plugin@5.5.0
│ └── github.com/fb55/htmlparser2?sponsor=1
│ └── htmlparser2@6.1.0
├── opencollective.com/postcss/
│ └── postcss@7.0.39, autoprefixer@10.4.2, postcss-js@4.0.0, postcss-load-config@3.1.1, postcss-nested@5.0.6
├── github.com/sponsors/jonschlinkert
│ └── picomatch@2.3.1
├── github.com/chalk/supports-color?sp...
│ └── supports-color@8.1.1
├── github.com/avajs/find-cache-dir?sp...
│ └── find-cache-dir@3.3.2
├── opencollective.com/typescript-eslint
│ └── @typescript-eslint/eslint-plugin@5.10.2, @typescript-eslint/scope-manager@5.10.2, @typescript-eslint/types@5.10.2, @typescript-eslint/visitor-keys@5.10.2, @typescript-eslint/type-utils@5.10.2, @typescript-eslint/utils@5.10.2, @typescript-eslint/typescript-estree@5.10.2, @typescript-eslint/parser@5.10.2, @typescript-eslint/experimental-utils@5.10.2
├── github.com/sindresorhus/emittery?s...
│ └── emittery@0.8.1
├── github.com/sindresorhus/execa?spon...
│ └── execa@5.1.1
├── github.com/chalk/wrap-ansi?sponsor=1
│ └── wrap-ansi@7.0.0
├─┬ github.com/chalk/strip-ansi?sponsor=1
│ │ └── strip-ansi@7.0.1
│ └── github.com/chalk/ansi-regex?sponsor=1
│ └── ansi-regex@6.0.1
├── ko-fi.com/mrcgrtz
│ └── postcss-opacity-percentage@1.1.2
├── opencollective.com/immer
│ └── immer@9.0.12
├── paulmillr.com/funding/
│ └── chokidar@3.5.3
└── github.com/sponsors/RubenVerborgh
└── follow-redirects@1.14.7

Collapse
 
adam_cyclones profile image
Adam Crockett 🌀

So this is just list of choices for libraries you want to pay money too. It's probably not what you wanted to do.

Collapse
 
adam_cyclones profile image
Adam Crockett 🌀

not errors, they're messages and if you read them carefully you will see what they mean.

Let's break it down:
Npm fund means that some people who make libraries want money to keep the lights on, you can run npm fund to pay them money

Added 23 packages means it installed just fine

And the security vulnerabilities are the things you should probably fix following the instructions.

I am not being sarcastic here, I swear, you seems to be new to npm.

The key here is to read the information presented to you and pick out anything you don't understand then ask a specific question 😊