Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TIMING is not a recognized command when running on windows machine. #7

Closed
shaohaolin opened this issue Feb 20, 2022 · 1 comment
Closed

TIMING is not a recognized command when running on windows machine. #7

shaohaolin opened this issue Feb 20, 2022 · 1 comment

Comments

@shaohaolin
Copy link

When run npm run lint at the root directory, packages would throw error when their npm run lint command starts with TIMING=1 in windows machine.

The fix is to add cross-env. Would you open to a PR for this?
@MahdiTa97
Copy link
Owner

The bug has been fixed in the v2.0.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shaohaolin @MahdiTa97