Security News
UK Officials Consider Banning Ransomware Payments from Public Entities
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
@keawade/using
Advanced tools
Provides a convenient syntax that ensures the correct use of Disposable or
Destroyable objects. That is, objects with either a dispose()
or destroy()
methods on them.
This pattern is used primarily to clean up connections to remote resources. For
example, the AWS SDK provides .destroy()
methods on many of their client
classes.
Call using
and for its first argument, pass it a resource or dictionary of
resources to be disposed or destroyed after the use context closes. For its
second argument, pass a function that will use the provided resources. When this
function's scope closes, the using
function will automatically call the
disposal methods on each resource.
Finally, a third argument can be optionally passed to either change the target
disposal method from .dispose()
to .destroy()
or to enable throwing on
errors.
By default, using
will attempt to call .dispose()
:
const createCustomer = async (customer: ICustomer) => {
// Value returned from provided function is returned
const createdCustomer = await using(
new Repository<Customer>(),
// Type is inferred
(customerRepository) => {
return customerRepository.create(customer);
// customerRepository.dispose() will be automatically called when the scope closes
},
);
return createdCustomer;
};
You can optionally specify to call .destroy()
instead:
const createCustomer = async (customer: ICustomer) => {
// Value returned from provided function is returned
const createdCustomer = await using(
new DynamoDBClient(dynamoDbConfig),
// Type is inferred
(dynamoDbClient) => {
const command = new DynamoDbPutCommand({
TableName: 'customer',
... // data, etc
})
return dynamoDbClient.send(command);
// dynamoDbClient.destroy() will be automatically called when the scope closes
},
// Must specify key to override default value of 'dispose'
{ key: 'destroy' },
);
return createdCustomer;
};
Instead of passing a single resource, you can pass a dictionary of resources and they will all be disposed or destroyed when the function closure exits.
const getUsersFavoriteRecipe = async (userId: string) => {
// Value returned from provided function is returned
const favoriteRecipe = await using(
{
userRepository: new Repository<User>(),
recipeRepository: new Repository<Recipe>(),
},
async ({
// Dictionary item types are inferred
userRepository,
recipeRepository,
}) => {
const user = await userRepository.get(userId);
return recipeRepository.get(user.favoriteRecipeId);
// userRepository.dispose() and recipeRepository.dispose() will be automatically called when the scope closes
}
);
return favoriteRecipe;
};
Same as earlier, you can override the key
to call .destroy()
instead.
throwOnError
You can provide the option throwOnError
to throw if the disposing method was
not found. This is intended for debugging during development and its use is
discouraged in production environments as it will throw immediately and will not
dispose remaining items in a dictionary.
FAQs
Using implementation for disposable resources.
The npm package @keawade/using receives a total of 11 weekly downloads. As such, @keawade/using popularity was classified as not popular.
We found that @keawade/using 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
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.