fix: update package.json scripts to use cross-env for env variable mgmt
#5087
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.
📝 Summary
Fix
make-fefailing in Windows by addingcross-envto remaining npm scripts that use env variables.Builds on #3242 which initially added
cross-envbut missed some scripts.🔍 Description of Changes
The
make fecommand was failing on Windows because several npm scripts infrontend/package.jsonwere using Unix-style environment variable syntax (e.g.,NODE_OPTIONS=--max-old-space-size=4096) which isn't recognized by Windows PowerShell/CMD.Added
cross-envprefix to all remaining scripts that set environment variables:The
cross-envpackage was already installed as a dev dependency from #3242, so no additional dependencies needed.📋 Checklist
📜 Reviewers
@akshayka OR @mscolnick