feat(scripts): add check-env preflight environment validation script#1421
Open
barnazaka wants to merge 6 commits intomidnightntwrk:mainfrom
Open
feat(scripts): add check-env preflight environment validation script#1421barnazaka wants to merge 6 commits intomidnightntwrk:mainfrom
barnazaka wants to merge 6 commits intomidnightntwrk:mainfrom
Conversation
feat(scripts): add check-env preflight script for environment validation
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 this PR does
Adds a
check-envpreflight script that developers can run beforestarting the Counter DApp to catch common setup issues early with
clear, actionable error messages.
Problem
New developers frequently hit silent failures because:
There's currently no automated way to catch these before running the DApp.
Solution
scripts/check-env.tsruns the following checks and outputspass/fail results with specific fix instructions:
Run with:
npm run check-env
Testing
Manually tested on macOS with:
Documentation
The script is self-documenting via its output. No docs changes
required as this is a developer tooling addition.
Checklist