loopback-datasource-juggler
Advanced tools
An ORM/ODM that provides a common set of interfaces for interacting with databases, REST APIs, and other types of data sources. It was originally forked from JugglingDB.
In LoopBack 4, it is part of the @loopback/repository module. See Repository page in LoopBack 4 for more details.
This module adopts the Module Long Term Support (LTS) policy, with the following End Of Life (EOL) dates:
| Version | Status | Published | EOL |
|---|---|---|---|
| 5.x | Current | Sep 2023 | Apr 2026 (minimum) |
| 4.x | Active | Oct 2018 | Apr 2025 |
| 3.x | End-of-Life | Dec 2016 | Dec 2020 |
| 2.x | End-of-Life | Jul 2014 | Apr 2019 |
Learn more about our LTS plan in the LoopBack documentation.
Install Juggler:
npm install loopback-datasource-juggler
Then install a connector:
npm install loopback-connector-mongodb // in this case, the mongodb connector
See the LoopBack documentation and DataSource page.
This project uses DCO. Be sure to sign off your commits. For details, see Contributing to LoopBack.
FAQs
LoopBack DataSource Juggler
The npm package loopback-datasource-juggler receives a total of 55,748 weekly downloads. As such, loopback-datasource-juggler popularity was classified as popular.
We found that loopback-datasource-juggler demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA denies CVE funding issues amid backlash over a new CVE foundation formed by board members, raising concerns about transparency and program governance.
Product
We’re excited to announce a powerful new capability in Socket: historical data and enhanced analytics.
Product
Module Reachability filters out unreachable CVEs so you can focus on vulnerabilities that actually matter to your application.