fix: add cross-env to support Windows dev script#970
Open
shun0619 wants to merge 1 commit 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.
🔄 Pull Request
📋 Type of Change (check all applicable)
📖 Description
What changed?
This PR fixes an issue where npm run dev fails on Windows because the environment variable syntax:
TURBOPACK=1 next dev --turbois not recognized by CMD or PowerShell.
To make the development script work across all platforms (Windows, macOS, Linux), I added cross-env and updated the dev script to:
"dev": "cross-env TURBOPACK=1 next dev --turbo"I also added cross-env to devDependencies so it installs automatically when users run npm install.
Why was this change made?
Windows contributors cannot start the development server due to the environment variable syntax error.
This creates a barrier for new contributors and prevents Windows users from running the project locally.
How does this change help users?
🔗 Related Issues
🧪 Testing & Quality Assurance
Testing Done (check all applicable)
Test Instructions
Expected Behavior
npm run devshould work on Windows, macOS, and Linux without environment variable errors.📸 Screenshots/Recordings
No UI changes.
Before
After
📋 Checklist
Code Quality
npm run type-check)npm run lint)npm run format)npm run build)Accessibility
Mobile & Responsive
Browser Compatibility
Documentation
Security & Privacy
🚀 Deployment Notes
📝 Additional Notes
This is a minimal, safe fix that improves cross‑platform compatibility and helps Windows contributors run the project without errors
👀 Reviewers
By submitting this PR, I confirm that: