You sort of brought this up already on a different thread and much like as has become apparent on that thread it’s not really clear what exactly you are expecting here. For instance, you keep saying API but you are not providing any context of what you mean by that.
Do you want to know the NodeJS API methods and documentation? Then that is available online:
MongoDB Node.JS Driver
You want to know the version? Then that was available in the
You want “version compatibility”? Then there’s a listing for that as well:
Node.js Driver Compatibility
If you want documentation on general MongoDB operations, then there are a number of sources being either:
Query and Projection Operators
Aggregation Pipeline Stages
Aggregation Pipeline Operators
mongo shell as bundled with the database distribution.
All of that said, the listed prerequisites are indeed slimmer than they should be:
We highly recommend taking M001 prior to taking this course. A basic understanding of MongoDB’s document model will help you get the most out of this course.
Therefore I would advise that in order for you to comfortably follow along with this course then you at least have:
A competent understanding of MongoDB CRUD operations, at the very least obtained from a full understanding of MongoDB CRUD Operations and ALL sub-sections of the related core documentation. Successful completion of M001 would be advised.
Prior working knowledge of working with NodeJS applications in general. Mostly since this is NOT a course in “Getting started with NodeJS” and having that exposure as a starting point should be a basic minimum.
For the most part though, the majority of lesson material quite fairly introduces you to topics and provides example usage for you to follow in many cases. Mostly each exercise will even point you to the relevant reference documentation as required for that particular section and the problems to be solved based on information that can be obtained from that reference source.
In the rare ( and I actually count one ) instance where a question might require you to “look up” something where it does not directly point you to the exact reference source, you should find that some people have already been *helpful" and provided a “link” to the relevant documentation source in this very forum, when you take the time to read the threads.
Of course, there is always the “internet” as a friend since you will find most questions you can come up with have generally been asked by someone else before. Even if not specifically in this discussion forum:
i.e “mongodb nodejs projection” as the literal search input to Google gives me a very accurate answer as to “what to do” within just a few links from the top of the page.
Finally, even if you are finding it hard to comprehend or keep up then the course material is still always “of value” since as you acquire greater knowledge then you should be able to refer back to the material and then understand it better at a later date.
And the answers are given too you, but quite naturally only after the assessment for each topic is complete.
Finally, not really clear what you mean by “Database editors”. I presume you want something like “code completion” on operations like aggregation pipeline stages such as
$lookup etc. I really don’t know of any things that do this outside of some rudimentary function in compass.
Personally, I never use them and have been doing this for a while now so I’m probably not the “new user” example. But I generally find the operator references ( first set of links given ) to be of greater use. And frankly I just “edit” in my current “general editor” of choice ( currently VSCode for what that’s worth ) and simply “Copy+Paste” the “text” into an open
mongo shell. Since (for me at least) that just works.
FYI, the majority of links presented in this page where simply obtained by me typing what was effectively the “page” or “section” titles ( or close variant of ) directly into a search engine and calling up that page. This is a really simple thing to do, and it yields results which should always be your very first step in obtaining information about anything.
Research first, then ask peers questions about “your research”. You will find people a lot more receptive to helping you when you can demonstrate effort and give them a base to understand what exactly you are asking.