
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
This is a simple library that provides a powerful abstraction for dealing with dependency injection both for system start up and for complex async tasks.
A simple example is as follows:
// File 1
const pdi = require("pdi")
pdi.add("db", () => DB.connect(options))
// File 2
const pdi = require("pdi")
pdi.add("dao", ["db"], ({ db }) => createDao(db))
// File 3
const pdi = require("pdi")
pdi.add("config", configObject)
// File 4
const pdi = require("pdi")
pdi.add(["dao", "config"], ({ dao, config }) => {
createServer(dao, config)
})
pdi
.start()
.then(logSuccess)
.catch(logError)
The api consists of:
add
Adds a factory function to the DI container. It offers a flexible API with 3 accepted signatures:
add(name, dependencies, factory)
- Registers a named factory function with dependencies. The factory will only be called when the dependencies are available. They will be passed in as arguments to the factory function.add(name, factory)
- A simpler form of the above where there are no dependencies.add(dependencies, factory)
- Registers a factory without a name. This is for side-effect functions.name
must be a string
dependencies
must be an array of strings
factory
can be either a value or a factory function. If it is not a function it will be wrapped with the always
function from Ramda
. If the factory is asynchronous then it should return a promise.
NB This function will be called with a single argument which is an object containing the required dependencies.
This function will throw on the following conditions:
start
This function accepts no arguments. It starts the DI container and returns a promise that will resolve when all factory functions have resolved.
The function will throw on the following conditions:
start
has already been calledThe function sorts all previously registered factory functions according to the dependency graph. It then calls as many factory functions in parallel as possible. If any of the functions throw then the promise will reject.
clear
This function clears all previously registered functions, it is mainly useful for testing.
strict
If this function is called before activation, then there are checks made when calling the factory fucntion, the following will cause an error to be thrown
create
This function is useful for where the DI container will be used to perform a particular operation, rather then for system start-up. It returns a DI container with the add
, start
, strict
and clear
methods.
While being small this library is powerful enough to be used for async flow control, for example:
const flow = pdi()
flow.add("body", req.body)
flow.add("userId", ["body"], path(["body", "userId"]))
flow.add("user", ["userId"], getUser)
flow.add("friends", ["user"], getFriends)
flow.add("result", ["friends", "user"], mergeFriendsAndUser)
flow
.start()
.then(({ result }) => res.send(result))
.catch(err => res.sendStatus(500))
Extra utils for testing:
pdi._test.clear()
pdi._test.
FAQs
Minimal Promise based dependency injection framework
The npm package pdi receives a total of 119 weekly downloads. As such, pdi popularity was classified as not popular.
We found that pdi demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.