
Security News
Vite+ Joins the Push to Consolidate JavaScript Tooling
Evan You announces Vite+, a commercial, Rust-powered toolchain built on the Vite ecosystem to unify JavaScript development and fund open source.
@nasriya/logify
Advanced tools
Versatile logging package for seamless integration and comprehensive error tracking.
Logify is a simple and powerful Node.js logging package.
Made with ❤️ in Palestine 🇵🇸
[!IMPORTANT] 🌟 Support Our Open-Source Development! 🌟 We need your support to keep our projects going! If you find our > work valuable, please consider contributing. Your support helps us > continue to develop and maintain these tools.
Every contribution, big or small, makes a difference. Thank you for > your generosity and support!
npm i @nasriya/logify
Import in ES6 module
import logify from '@nasriya/logify';
Import in CommonJS (CJS)
const logify = require('@nasriya/logify').default;
You can configure the logify
instance to suite your needs. Here's how you can configure it:
logify.config({
/**The name of the running service or process. Default: `process.pid` */
service: 'myTestApp',
/**Set different handlers for more robust error handling */
handlers: {
uncaughtException: (error: Error, origin) => {
// handle uncought exeptions; for example:
logify.log(error); // Logs the error
}
},
/**An absolute path to the directory where you want the logs to be stored at. Default: The project directory. */
logLocation: `\\\\10.0.0.217\\Dev\\myTestApp` // A network location or a local directory
})
Note: All configurations are optional.
Here are some examples as of how to use the Logify package.
Whenever needed, you can throw a new AppError
. Errors created from this class are automatically logged.
throw new logify.errors.AppError({ message: 'An error has occurred' });
// ⇨ AppError: An error has occurred
You can also throw errors with additional data if you want:
throw new logify.errors.AppError({
message: 'Unauthorized user',
name: 'HTTP',
severity: 'Low'
});
// ⇨ HTTP: Unauthorized user
Note: If you only want to log the error, do NOT throw
the error.
You can use predefined middlewares designed for specific server frameworks like HyperCloud or Express.js.
The middlewares can be accessed by:
const hypercloudMiddleware = logify.middlewares.hypercloud;
console.log(typeof hypercloudMiddleware); // ⇨ function
Logify doesn't only log errors and incoming requests, you can log pretty much anything you want to the console as well as in the logs files.
const message = 'Hello World!'
const user = { name: 'John Doe', dob: new Date('1985-05-10') }
const error = new Error('A test error');
logify.logger.log(message); // Log a string
logify.logger.log(user); // Log an object
logify.logger.log(error); // Log an error
Thank you.
Please read the license from here.
FAQs
Versatile logging package for seamless integration and comprehensive error tracking.
We found that @nasriya/logify demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 open source maintainers 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
Evan You announces Vite+, a commercial, Rust-powered toolchain built on the Vite ecosystem to unify JavaScript development and fund open source.
Security News
Ruby Central’s incident report on the RubyGems.org access dispute sparks backlash from former maintainers and renewed debate over project governance.
Research
/Security News
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.