Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
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.
// simple dependency providing
// provider.mjs
import Carafe from 'carafe'
const container = new Carafe();
container.register('water', 'fresh and cool');
export default container;
// status.mjs
import container from 'provider.mjs';
// get happens in the function so it always gets the current value
const waterStatus = () => container.get('water');
export default waterStatus;
// status.mjs, alternatively using inject
import container from 'provider.mjs';
// the function returned always gets the updated dependency
const waterStatus = container.inject(['water'], (water) => water);
export default waterStatus;
// consumer.mjs
import status from 'status.mjs';
console.log(status()); // fresh and cool
You can also opt in to dependency replacement by passing true as the only argument to Carafe.
// dependency replacement
// provider.mjs
import Carafe from 'carafe'
const allowReplace = process.env.NODE_ENV === 'test'; // optionally enable replacement
const container = new Carafe(allowReplace);
container.register('water', 'fresh and cool');
export default container;
// status.mjs does not change
const waterStatus = container.inject(['water'], (water) => water);
export default waterStatus;
// then in your tests...
import container from 'provider.mjs';
import status from 'status.mjs';
container.replace('water', 'mock water');
console.log(status()); // mock water
container.restore('water'); // or to restore all mocks, use restore()
console.log(status()); // fresh and cool
Carafe instances should be new
ed up, and the instance returned will have the following methods. You can call Carafe() as well, and it will return a new instance for you.
Creates and returns a new instance of Carafe. If enableReplacement
is true, dependencies can be replaced.
Registered a new dependency by name. name
should be a string, and the method will throw if it's not.
Returns a registered dependency by name. If there is no matching depdendency, the method will throw.
Takes an array of named depdendencies, passing them in order as arguments to function
. Returns the original function
with the depdendencies partially applied.
Only available if enableReplacement
is true
Used to replace a dependency's value in a recoverable way. replace
can be called multiple times, and the resulting value when get
is used will always be whatever the last value provided was. Use restore
to restore the original dependency's payload.
Only available if enableReplacement
is true
Used to restore a given dependency to its original registered value, undoing any replace
calls. If no name is provided, all dependencies are restored.
MIT © w33ble
FAQs
Crazy simple dependency container
The npm package carafe receives a total of 6 weekly downloads. As such, carafe popularity was classified as not popular.
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
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.