mongoose-paginate | Mongoose.js Document Query Pagination | SQL Database library

I hope I am not missing something. As stated in https://www.npmjs.com/package/mongoose-paginate-v2

Solution - searching missions colection

Because full text search query must be the first stage in the aggregation pipeline, it is not currently possible to perform full text search in two collections as part of the same query.

You'll need to reorganize your data.

You need to check if the docs property is not undefined. You can do that in a couple of ways:

1. You can use optional chaining to check if the property is not null or undefined. Then your code will look like this this.props.results.data?.docs.map.... Here's how you add it to your react app (but if you are using the latest babel version - it should work out of the box)

2. You do the check yourself. The most basic one is, as suggested in the comment, is to check if the property is falsy:

You can run two separate queries using $facet:

Finally it solved by copy and pasting .graphql files inside the build/apollo by this command

You'll have to use npm audit and actually read the audit log. In there will be advice on which versions can be installed to fix vulnerabilities.See https://docs.npmjs.com/cli/audit for more information on npm audit.

You can get a report of all vulnerabilities using npm audit. In that report for each vulnerability you will also see a way to fix it. When you use npm audit fix you are telling npm to execute those fixes. Npm however will not automatically install fixes that might break your project, such as major versions changes. You'll have to manually execute the npm install commands for those if you decide the vulnerability is more important than having to deal with the possible breaking change.

Another common warning are peer dependency warnings. Peer dependencies specify not dependency, but compatibility. Check out this post for a way better explanation on peer dependencies: https://stackoverflow.com/a/34645112/1016004

You can see a peer dependency warning for 2 reasons: the specified peer dependency is missing, or the peer dependency is of the wrong version. In both cases you will have to figure out the correct response yourself. The core question to answer is whether you can install the dependency in your project:

• Do you use any deprecated features that will be removed in an update, do any breaking changes apply to your code, ...?
• Do you have to revert to a version with a known vulnerability that you use in such a way that it might endanger user data, ... ?

The simple solution, not recommended for production, is to just manually try to run npm install for both the vulnerabilities and peer dependencies with the proposed versions. Be sure to have version control or backups so that you can revert if you end up with more errors than you started with.

If the simple solution doesn't cut it you'll have to look for other versions of packages that are part of the unsolvable constraints. Maybe previous versions of any of those packages can work together?

Below line:

Use regex function