Consider allowing DEST_DIR be set to in [nodeenv] config section

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js, python
Domain
cli, tooling

Research direction

Start by locating the [nodeenv] configuration handling and the command-line path for DEST_DIR. Determine how a config value should interact with the existing command-line option, then verify that setting DEST_DIR in the config produces the same destination behavior.

Written by the indexing model from the issue text.

Description

new-feature

Hi!

Thank you for the great project. I am wondering if you would be willing to accept a PR for setting DEST_DIR in the configuration settings?

I have a dockerized project which I use nodeenv in. Since its dockerized, we (for better or worse) dont use a venv, so rely on passing DEST_DIR on the commandline. Instead of aligning everywhere which may use nodeenv, I figure it may be valuable to just set it in config.

Any thoughts? If you are happy to have this option, I can make the change!

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.