Crazy simple dependency container.
def. a wide-mouthed glass or metal bottle with a lip or spout, for holding and serving dependencies
A little inspiration taken from @travi/ioc.
Create a Carafe instance, add dependencies to it, and get them back out where needed.
// provider.mjs
import Carafe from 'carafe'
const container = new Carafe();
container.add('water', () => 'fresh and cool');
export default container;
// elsewhere.mjs
import container from 'provider.mjs';
const water = container.get('water');
return water(); // fresh and cool
// in your tests...
import container from 'provider.mjs';
import elsewhere from 'elsewhere.mjs';
container.replace('water', () => 'mock water');
elsewhere(); // mock water
container.restore('water'); // or to restore all mocks, use restore()
elsewhere(); // fresh and cool
MIT © w33ble
FAQs
Crazy simple dependency container
We found that carafe 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.