Open-Trader/opentrader

`moon run prisma:migrate` exited with error "Environment variable not found" on Windows

Open

#96 opened on Jan 9, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)TypeScript (319 forks)auto 404
buggood first issue

Repository metrics

Stars
 (2,749 stars)
PR merge metrics
 (PR metrics pending)

Description

I can confirm that this is reproducible only on Windows.

Reproduction steps:

  1. Follow installation steps from CONTRIBUTING.md

  2. Next, generate Prisma client:

moon run prisma:migrate

Command failed: "Environment variable not found"

image

Workaround:

If the command is executed as follows, it works fine:

pnpm exec prisma migrate dev --schema packages/prisma/src/schema.prisma

For some reason Prisma does not load the ENV variables from .env file, so the schema must be specified manually.

Contributor guide

Research direction
Inspect the moon configuration and Prisma schema path handling on Windows. Check how moon executes tasks and whether it properly sets environment variables from .env files. The workaround suggests that the schema flag resolves the issue, indicating that the default schema path may not be correctly resolved when moon runs the command.
Tech stack
typescriptnodejsprisma
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
WindowsNode.jspnpmmoon
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60