Skip to content

Conversation

@snowystinger
Copy link
Member

@snowystinger snowystinger commented Apr 17, 2021

This speeds up the overall performance of running yarn lint on most machines. Lint alone on my machine takes ~109s. TSC takes another ~30s. When run in series this is over 2min. However, when run in parallel, the entire command only takes ~109s, in otherwords only as long as the longest process.

In our pipeline, the difference is slightly less noticeable ~15s of savings
However, since it's still eslint that is taking the longest, we only have to address that one to get full savings. The other two do not matter in this scenario.

Another added benefit though is that if you fail any step, you'll still get the results of the other two tasks. So you won't fix typescript only to be surprised with a lint error.

Closes

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

This speeds up the overall performance of running `yarn lint` on most machines. Lint alone on my machine takes ~109s. TSC takes another ~30s. When run in series this is over 2min. However, when run in parallel, the entire command only takes ~109s, in otherwords only as long as the longest process.
@adobe-bot
Copy link

Build successful! 🎉

1 similar comment
@adobe-bot
Copy link

Build successful! 🎉

@devongovett devongovett merged commit 79b8d0b into main Apr 19, 2021
@devongovett devongovett deleted the speed-up-lint branch April 19, 2021 21:15
majornista pushed a commit to majornista/react-spectrum-v3 that referenced this pull request May 19, 2021
This speeds up the overall performance of running `yarn lint` on most machines. Lint alone on my machine takes ~109s. TSC takes another ~30s. When run in series this is over 2min. However, when run in parallel, the entire command only takes ~109s, in otherwords only as long as the longest process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants