CLI path option?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- cli
Research direction
Start by locating the CLI entry point and the plugin-option parsing used by the command shown in the issue. Reproduce the requested --path usage with .env-prod and script.js, then establish how a supported path option should be specified and what successful variable inlining should look like.
Written by the indexing model from the issue text.
Description
How can I pass a specific path to the CLI command? For instance like this:
$ babel --plugins [ inline-dotenv --path .env-prod ] script.js
- Dominant language
- JavaScript
- Stars
- 123
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from brysgo/babel-plugin-inline-dotenv
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
brysgo/babel-plugin-inline-dotenv#39 · 3 comments · 10 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
brysgo/babel-plugin-inline-dotenv#38 · 2 comments · 4 reactions ·
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 25/100
brysgo/babel-plugin-inline-dotenv#23 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
brysgo/babel-plugin-inline-dotenv#13 · 16 comments · 1 reaction ·
All issues in brysgo/babel-plugin-inline-dotenv
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bigcapitalhq/bigcapital#1544 · 1 comment ·
Maintainers usually reply within 1 day
-
help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
meshery/meshery.io#3112 ·
Maintainers usually reply within 2 days
-
area:docs type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bulkhead-labs/tailsuite#31 ·
-
dependencies javascript
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
gems-uff/noworkflow#470 ·
Maintainers usually reply within 3 days
-
product / auth product / console product / sites product / storage
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day