npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

mongoose-backref

v1.0.2

Published

A back reference plugin for mongoosejs

Downloads

6

Readme

This is a Mongoose plugin that handles back references. You can define a back reference on any references or array of references in the source Schema. Whenever the a document of the source Schema type has that field changed, the target document will have its back references updated:

Foo {bar: {ref: 'Bar', backref: 'foos'}} Bar {foos: [{ref: 'Foo'}]}

In the above, anytime Foo.bar is changed, the related Bar.foos is updated. Note that this is not bi-directional! If Bar.foos is changed, Foo.bar is NOT updated. In order to do that, you need to define a reverse back reference:

Foo {bar: {ref: 'Bar', backref: 'foos'}} Bar {foos: [{ref: "Foo', backref: 'bar'}]}

In the above, any updates to Foo.bar is same as before, but in addition, any changes to Bar.foos get updated too (in this case, if a Foo is removed from Bar.foos, that Foo's Foo.bar will be set to null). Note that in this particular instance, you want to really make sure this is the right behavior for your model relationship. For example, as defined above, one could add the same Foo to multiple Bar.foos, in which case the last Bar that added Foo would have it referenced in Foo.bar. In order to deal with this, you might want to have a many-to-many relationship:

Foo {bars: [{ref: 'Bar', backref: 'foos'}]} Bar {foos: [{ref: "Foo', backref: 'bars'}]}

In this case, Foo.bars is an array of references, so many-to-many relationships are supported.