Introduce logging framework/library

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js, typescript
Domain
tooling

Research direction

The issue names no files, tests, or entry points. Start by reviewing the proposed console and winston approaches, including their browser and Node.js behavior; done means agreeing on a customized logger design that supports the stated environments and output options.

Written by the indexing model from the issue text.

Description

The vanilla console.log/warn/error is convenient, and works on both client-side (browser) and server-side(e.g. nodejs) apps. But it only prints to stdout/stderr.

Popular logging frameworks like winston is powerful, providing different log levels, different format of output (stdout, a file, and a database etc.). But is not directly working on client-side so far, and introduce more dependencies.

A feasible solution is using a customized logger, and delegate logger.log to console.log or winston based on running environment.

Dominant language
TypeScript
Stars
19
Forks
6
Avg merge
2d 3h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/FeatureManagement-JavaScript

All issues in microsoft/FeatureManagement-JavaScript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.