# @armit/logger

> Simple, pretty and powerful logger for nodejs

Latest version **0.3.0** (published 2025-06-01) · MIT license · 0 weekly downloads

## Install

```sh
npm install @armit/logger
pnpm add @armit/logger
yarn add @armit/logger
bun add @armit/logger
```

## Health

**Score 50/100 (C)** — status: stable.

Positive: has types; esm support; no vulnerabilities; high quality score.

Warnings: low downloads; pre 1.0.

Negative: stale.

## Facts

| | |
|---|---|
| Version | 0.3.0 |
| Published | 2025-06-01 |
| First published | 2022-12-26 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | bundled |
| Module format | ESM |
| Node | >=18.0.0 |
| Dependencies | 0 |
| Unpacked size | 27.9 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 3 |
| Author | Yingchun Tian |
| Maintainers | tianyingchun, hyperse.net |

## Links

- npm: https://www.npmjs.com/package/@armit/logger
- Repository: https://github.com/armitjs/armit
- Issues: https://github.com/armitjs/armit/issues
- npm.io page: https://npm.io/package/@armit/logger

## Recent versions

- 0.3.0 (latest) — 2025-06-01
- 0.2.11 — 2025-03-31
- 0.2.10 — 2025-03-11
- 0.2.9 — 2025-02-10
- 0.2.8 — 2024-12-24
- 0.2.7 — 2024-11-21
- 0.2.6 — 2024-10-13
- 0.2.5 — 2024-09-06
- 0.2.4 — 2024-07-24
- 0.2.3 — 2024-07-15
- 0.2.2 — 2024-06-20
- 0.2.1 — 2024-06-13
- 0.2.0 — 2024-06-12
- 0.1.5 — 2024-05-13
- 0.1.4 — 2024-04-02
- … 28 more at https://npm.io/package/@armit/logger/versions

## README

# Armitjs

A elegant small typescript based front-end dev-kits that includes most usefull feature for develop `miniprogram`

<p align="left">
  <a aria-label="Build" href="https://github.com/armitjs/armit/actions?query=workflow%3ACI">
    <img alt="build" src="https://img.shields.io/github/actions/workflow/status/armitjs/armit/ci-lib-cli.yml?branch=main&label=CI&logo=github&style=flat-quare&labelColor=000000" />
  </a>
  <a aria-label="LoC">  
    <img alt="LoC" src="https://img.shields.io/tokei/lines/github/armitjs/armit?style=flat-quare&labelColor=000000" />
  </a>
  <a aria-label="Top language" href="https://github.com/armitjs/armit/search?l=typescript">
    <img alt="GitHub top language" src="https://img.shields.io/github/languages/top/armitjs/armit?style=flat-square&labelColor=000&color=blue">
  </a>
  <a aria-label="Licence" href="https://github.com/armitjs/armit/blob/main/LICENSE">
    <img alt="Licence" src="https://img.shields.io/github/license/armitjs/armit?style=flat-quare&labelColor=000000" />
  </a>
</p>

## Development

The following instructions are for those who want to develop the armit core framework or plugins (e.g. if you intend to make a pull request). For instructions on how to build a project _using_ Armit, please see the [Getting Started guide](https://www.armitjs.io/docs/getting-started/).

### 1. Install top-level dependencies

`yarn`
`npm install commitizen -g`

The root directory has a `package.json` which contains build-related dependencies for tasks including:

- Building & deploying the docs
- Generating TypeScript types from the GraphQL schema
- Linting, formatting & testing tasks to run on git commit & push

### 2. Switch yarn to berry

- `yarn set version berry`
- `yarn plugin import workspace-tools`
- `yarn install`

This runs the yarn "install" command, will scan those directories and look for children `package.json`. Their content is used to define the workspace topology (core, common, dependencies...), and cross-links monorepo dependencies.

### 3. Build & test all packages

- `yarn g:test-unit`
- `yarn g:lint`
- `yarn g:typecheck`
- `yarn g:build`

### 4. Publishing

> Optional

If you need to share some packages outside of the monorepo, you can publish them to npm or private repositories.
An example based on tsup is present in each package. Versioning and publishing can be done with [atlassian/changeset](https://github.com/atlassian/changesets),
and it's simple as typing:

```bash
$ yarn g:changeset
$ git cz
```

Follow the instructions... and commit the changeset file. A "Version Packages" P/R will appear after CI checks.
When merging it, a [github action](./.github/workflows/release-or-version-pr.yml) will publish the packages
with resulting semver version and generate CHANGELOGS for you.

### 5. Maintaining deps updated

The global commands `yarn deps:update` will help to maintain the same versions across the entire monorepo.
They are based on the excellent [npm-check-updates](https://github.com/raineorshine/npm-check-updates)
(see [options](https://github.com/raineorshine/npm-check-updates#options), i.e: `yarn check:deps -t minor`).

> After running `yarn deps:update`, a `yarn install` is required. To prevent
> having duplicates in the yarn.lock, you can run `yarn dedupe --check` and `yarn dedupe` to
> apply deduplication. The duplicate check is enforced in the example github actions.

### 6. Editor support

> 6.1 VSCode

The armit have full setting for vscode workspace (`armit.code-workspace`) that the `eslint.workingDirectories` setting is set: just open it.

More info [here](https://github.com/microsoft/vscode-eslint#mono-repository-setup)

---
_Source: https://npm.io/package/@armit/logger · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._