search

quantified-uncertainty / metaforecast

Fetch forecasts from prediction markets/forecasting platforms to make them searchable. Integrate these forecasts into other services.
https://metaforecast.org/
MIT License
60 stars 6 forks source link

npm errors #16

Closed NunoSempere closed 2 years ago

NunoSempere commented 2 years ago

I'm getting a fair number of npm errors:

npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated rollup-plugin-inject@3.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated statsd-client@0.4.7: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated node-pre-gyp@0.13.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

In addition, the project maybe somehow depends on npm.team.kocherga.club. Is this really necessary? I think this also ended up affecting the heroku build: https://dashboard.heroku.com/apps/metaforecast-backend/activity/builds/5760aab8-f054-484e-ae71-10eca5f1fe40

berekuk commented 2 years ago

I'm getting a fair number of npm errors

Most of these seem like deps of netlify-cli. I think we can just ignore all of these, and nothing bad will happen. npm can be excessive with its audit and outdated checks.

In addition, the project maybe somehow depends on npm.team.kocherga.club.

Ugh, that wasn’t intentional. It was set up in my ~/.npmrc and leaked into package-lock.json automatically.

s/npm.team.kocherga.club/registry.npmjs.org/g & pushed, should be fixed now.

NunoSempere commented 2 years ago

I think we can just ignore all of these, and nothing bad will happen. npm can be excessive with its audit and outdated checks.

Makes sense, I'll trust you on this.