Switch console logging to use @logtail/js

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, typescript
Domain
observability-sre

Research direction

No source files or tests are named; start by locating the app's existing console logging and read the linked @logtail/js browser and Node.js installation guide. Use test-driven development to verify that logs go through the package and that its overridden .send writes to stderr rather than sending over HTTP; done means all existing console logs are covered.

Written by the indexing model from the issue text.

Description

Please replace all the existing console logs in the app with the npm @logtail/js package.

Quick start docs are here:

https://betterstack.com/docs/logs/javascript/install/#logging-from-browser-and-node-js

Be sure to override .send with a logger that writes to stderr instead of sending over HTTP to someplace.

Use test-driven-development.

Dominant language
TypeScript
Stars
8
Forks
3
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 mozilla/skylight

All issues in mozilla/skylight

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.