Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Switch between two .env files - for prod and dev

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, react-native
Domain
mobile, tooling

Research direction

The issue concerns the plugin's handling of .env and .env.production in an Expo/React Native setup; start with the linked integration steps and the plugin's configuration entry point. Done means establishing whether separate development and production files can be selected, then documenting or implementing the supported behavior and validating it in the reported setup.

Written by the indexing model from the issue text.

Description

Hi. I've integrated this plugin on my Expo (React Native) project following these steps.

Can you please tell me if it is possible to configure the plugin to use the .env file for development and another file, .env.production, for production?

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

  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 brysgo/babel-plugin-inline-dotenv

All issues in brysgo/babel-plugin-inline-dotenv

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.