-
Notifications
You must be signed in to change notification settings - Fork 248
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.
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
(chore) Remove timing env from lint script in all packages #1679
Conversation
Size Change: 0 B Total Size: 10.7 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me @denniskigen
Mind looking at this one too, @pirupius openmrs/openmrs-esm-patient-management#990 |
@@ -12,7 +12,7 @@ | |||
"debug": "npm run serve", | |||
"build": "webpack --mode production --color", | |||
"analyze": "webpack --mode=production --env analyze=true", | |||
"lint": "cross-env TIMING=1 eslint src --ext tsx,ts --fix --max-warnings=0", | |||
"lint": "cross-env eslint src --ext tsx,ts --fix --max-warnings=0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could drop the cross-env
here too, since the only reason for that is to allow TIMING=1
....
Requirements
Summary
I've removed the ESLint TIMING environment variable from the
lint
scripts across all packages in this repo.Adding this variable used to be a recommendation for earlier versions of turbo (I can't find a link to where exactly in a past copy of the docs), but it has since been removed. This is likely because turbo caches logs to
stdout
andstderr
by default. This means caching and parallelization should not be affected by this change.Screenshots
Related Issue
Other