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

Relative paths

Open
#2 7 comments 0 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Start by tracing how the Babel plugin and dotenv resolve relative paths, using the reported '../../.env' case from the Lerna setup as the reproduction. Compare the behavior with the fork mentioned in the issue and determine a project-approved handling for the path; done means the reproduction no longer fails and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Description

This seems to be a common issue with babel plugins, we're doing relative reads (or dotenv ends up doing relative read), so a path with something like '../../.env' (lerna setup, I know :() starts failing.
Solved in a fork but wondering how to handle or whether to relay upstream.

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.