Product
Introducing License Enforcement in Socket
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
@diotoborg/aliquam-ut
Advanced tools
TypeScript logging can be used to add logging to your web or node project.
TypeScript logging can be used to add logging to your web or node project.
Version 2 of @diotoborg/aliquam-ut has been written from scratch and is not compatible with version 1 (see migration).
There are two different flavors available to use. Please visit the documentation of the links below and pick the one you prefer.
Node Channel (NEW)
Supports logging to files and file rollover. Please see @diotoborg/aliquam-ut-node-channel for details.
Documentation
The following sections are available:
Using @diotoborg/aliquam-ut version 1?
Please visit https://github.com/diotoborg/aliquam-ut/tree/release-1.x for more details. Consider upgrading to the latest version.
Version 2 of @diotoborg/aliquam-ut is not compatible with version 1
Please check the migration guide for more information.
For all details and documentation please visit the links above. The following sections provide a quick start only for both flavors.
To install the category-style flavor use the following npm commands:
npm install --save @diotoborg/aliquam-ut # Core is required for any style
npm install --save @diotoborg/aliquam-ut-category-style
Usage
The following section configures a provider and exposes a getLogger function for other modules to use. The getLogger in this example is used to create root categories.
/*--- LogConfig.ts ---*/
import {CategoryProvider, Category} from "@diotoborg/aliquam-ut-category-style";
const provider = CategoryProvider.createProvider("ExampleProvider");
export function getLogger(name: string): Category {
return provider.getCategory(name);
}
/*--- Person.ts ---*/
import {getLogger} from "./LogConfig";
/* Root categories can and probably will be defined elsewhere, this is just an example */
const logModel = getLogger("model");
/* Create child categories based on a parent category, effectively allowing you to create a tree of loggers when needed */
const logPerson = logModel.getChildCategory("Person");
function example(value: string) {
logPerson.debug(() => `Example function called with value ${value}`);
try {
// Awesome code here...
logPerson.getChildCategory("example()").debug(() => "Child category again");
}
catch (e) {
logPerson.error(() => "Awesome code failed unexpectedly", e);
}
finally {
logPerson.debug(() => "Example function completed");
}
}
To install the log4ts-style flavor use the following npm commands:
npm install --save @diotoborg/aliquam-ut # Core is required for any style
npm install --save @diotoborg/aliquam-ut-log4ts-style
Usage
The following section configures a provider and exposes a getLogger function for other modules to use.
/*--- LogConfig.ts ---*/
import {LogLevel} from "@diotoborg/aliquam-ut";
import {Log4TSProvider, Logger} from "@diotoborg/aliquam-ut-log4ts-style";
const provider = Log4TSProvider.createProvider("ExampleProvider", {
/* Specify the various group expressions to match against */
groups: [{
expression: new RegExp("model.+"),
level: LogLevel.Debug, /* This group will log on debug instead */
}, {
expression: new RegExp("service.+"),
}],
});
export function getLogger(name: string): Logger {
return provider.getLogger(name);
}
/*--- Person.ts ---*/
import {getLogger} from "./LogConfig";
const log = getLogger("model.Person")
function example(value: string) {
log.debug(() => `Example function called with value ${value}`);
try {
// Awesome code here...
}
catch (e) {
log.error(() => "Awesome code failed unexpectedly", e);
}
finally {
log.debug(() => "Example function completed");
}
}
Please make sure to have node 18 LTS installed.
To locally build the logging flavors. The easiest is to run the ./initialize.sh script:
./initialize.sh # Clean, install and build everything.
This will cleanly install and build your branch from scratch.
You can also manually install things, by going into the respective directories and manually type:
# If not installed yet
npm run ci
# or for the test projects
npm install
Any project when you're in the respective directory can be built with:
npm run build
That will clean, build and test the project.
To locally run the tests, in the respective directories:
npm run test
If you're on linux or mac-os, it's easiest to run initialize.sh first. Otherwise, skip that and run npm run install
manually as shown below.
# Linux/MacOS only - Cleans everything and re-installs packages, including those for the integration projects.
./initialize.sh
# If not using ./initialize.sh, note that the dependent projects must be built first (core and the various styles, see above)
npm run install # Run inside respective test-integration project, e.g. tests-integration/rollup
npm run build # Run inside respective test-integration project. Builds test webapp and runs cypress tests.
If you encounter a bug please log it in the issue tracker of this repository and make sure to specify what flavor (style) you are using.
Feel free to contribute or come up with great ideas, please use the issue tracker for that.
If you add/change new functionality and want it merged in a later release, please open a pull request. Also add tests for it (see various "test" directories).
Please keep in mind that things may not fit the library and in such case will be rejected, so if you are unsure please ask first before wasting your valuable time.
Please check the migration guide if you are on an old version and wish to use the latest version available.
Please check the changelog
FAQs
TypeScript logging can be used to add logging to your web or node project.
The npm package @diotoborg/aliquam-ut receives a total of 64 weekly downloads. As such, @diotoborg/aliquam-ut popularity was classified as not popular.
We found that @diotoborg/aliquam-ut demonstrated a healthy version release cadence and project activity because the last version was released less than 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.
Product
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
Product
We're launching a new set of license analysis and compliance features for analyzing, managing, and complying with licenses across a range of supported languages and ecosystems.
Product
We're excited to introduce Socket Optimize, a powerful CLI command to secure open source dependencies with tested, optimized package overrides.