CI, .env loading, NODE_ENV flags, cleanup - #7
Open
webbertakken wants to merge 12 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
main, Node 18/20/22 via corepack pnpm with cache.--production/--development: setNODE_ENVfor the wrapped script. Flag beats ambient; passing both errors. Added a--separator so script args pass through verbatim; envoke flags are never forwarded..envloading (viadotenv): reads.env*from repo root + cwd (deduped). Precedence: real env > flag NODE_ENV > cwd files > root files; within a dir.env.[mode].local>.env.[mode]>.env.local>.env. Real env is never overwritten; mode files load only whenNODE_ENVis known.## Todoremoved.yarn.lock+.yarnrc.yml, fixprepublishOnlyto pnpm, bump0.2.0.Testing
pnpm typecheck && pnpm build && pnpm testgreen (exit-codes, flags, dotenv suites).act(job succeeded).Note
0.2.0is not published in this PR; tagging/publish happens after merge.