make nodeenv usable as library - split main and logging config into sep. file

Open
#185 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
28/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
nodejs, python
Domain
cli, tooling

Research direction

Start by locating the nodeenv module's main entry point and its logging configuration; the issue does not name specific files or tests. Done means the logging setup is separated from the main/library path so importing nodeenv no longer disturbs a caller's test results.

Written by the indexing model from the issue text.

Description

enhancement

the way you configure logging makes it difficult to use as a library (at least it totally disturbs my test results). For now I fixed and included the nodeenv file with my code (but I do not like that much).
I am happy to do the split and submit a PR in case you decide that you want to go into that direction.

Dominant language
Python
Stars
1.8k
Forks
222
Avg merge
11h 11m
Merged PRs (30d)
12

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 ekalinin/nodeenv

All issues in ekalinin/nodeenv

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.