Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
flacon is a dependency injection container with a clean and tiny API that helps you to test your components individually. .5k
minified & gzipped.
require
calls.npm install flacon
Imagine you have a service foo.js
.
module.exports = {
value: () => 'foo'
}
Now you want another service bar.js
that uses foo.js
.
const foo = require('./foo')
module.exports = {
value: () => foo.value() + 'bar'
}
This looks all good. But when testing bar.js
, mocking foo.js
is really difficult because it is a private dependency. flacon, on the other hand, forces you to explicitly declare all dependencies, making it easy to mock them.
First, we create a new container in container.js
. On a container, you can publish and load modules.
const Flacon = require('flacon')
module.exports = new Flacon()
Let's start with foo.js
. We call the publish
method with an id and a factory function.
const container = require('./container');
container.publish('foo', () => ({
value: () => 'foo'
}))
Moving on to bar.js
, we define foo
as a dependency. The result of foo
's factory will be passed into bar
's factory.
const container = require('./container')
const factory = (foo) => ({
value: () => foo.value() + 'bar'
})
factory.deps = ['foo']
container.publish('bar', factory)
By simply calling the container with a module id, you will get the return value of the factory function.
const container = require('./container')
const bar = container('bar')
bar.value() // -> 'foobar'
During testing, we can easily manipulate or mock a dependency. This will load every mocked module without caching.
const container = require('./container')
const bar = container('bar', {
foo: (foo) => ({
value: () => 'baz'
})
})
bar.value() // -> 'bazbar'
Note: In a mock function, make sure to never manipulate given module, always return a new one!
flush
To force flacon to call a module's factory again, use flush
.
container.load('foo') // factory creates module
container.flush('foo')
container.load('foo') // factory creates module again
flacon(id, [mocks])
Loads a module by id
. Caches and returns the module.
mocks
is an object of mocking functions by id. Mocked dependencies will not be cached.
id
: The identifier, unique to the container.mocks
: A map of callbacks, mapped by module id
. The return value of each callback will be the mock.flacon.publish(id, factory)
Registers a module by id
. Reads the module's dependencies from factory.deps
. Returns the module's factory
.
id
: The identifier, unique to the container.factory
: A function, taking the dependencies, that returns the module.flacon.flush()
Removes a module from the cache. Returns the container.
id
: The identifier, unique to the container.If you have a question, found a bug or want to propose a feature, have a look at the issues page.
FAQs
A hyperminimal dependency injection framework.
We found that flacon 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.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.