@loopback/booter-lb3app
Advanced tools
A booter component for LoopBack 3 applications to expose their REST API via LoopBack 4
Boot a LoopBack 3 application and expose its REST API via LoopBack 4.
The @loopback/booter-lb3app package provides a way for LoopBack 3 developers
to boot their LoopBack 3 application, convert the application's Swagger spec
into OpenAPI v3, and then mount the application, including its spec, onto a
target LoopBack 4 application.
npm install --save @loopback/booter-lb3app
Import the component at the top of your src/application.ts file.
import {Lb3AppBooterComponent} from '@loopback/booter-lb3app';
Register the component in Application's constructor:
this.component(Lb3AppBooterComponent);
By default, the LoopBack 3 models and datasources will be bond to the application with naming conventions as:
lb3-datasources.{ds name}lb3-models.{model name}Run npm test from the root folder.
See all contributors.
MIT
FAQs
A booter component for LoopBack 3 applications to expose their REST API via LoopBack 4
The npm package @loopback/booter-lb3app receives a total of 576 weekly downloads. As such, @loopback/booter-lb3app popularity was classified as not popular.
We found that @loopback/booter-lb3app 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.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.