-
Notifications
You must be signed in to change notification settings - Fork 39
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
Improve build performance #733
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
ea1f8b0
add all changes and github action cache
hmorgancode 1ee5fe6
fix actions I think
hmorgancode de64347
downgrade to node 16 for now
hmorgancode 90197a7
update actions
hmorgancode 1242196
undo prev ci change
hmorgancode a9c41ef
skip unrelated test fails, and add some updates
hmorgancode 15dd7fb
cypress fix attempt #1
hmorgancode 9867986
restore skipped tests and use regular ts-loader for code coverage builds
hmorgancode 8c38f8e
fix github actions caching I think
hmorgancode a846e4e
last try at fixing caching
hmorgancode 987a9ba
last iteration, kirk, i promise
hmorgancode 6ca514b
i lied
hmorgancode a33da3f
no for real this time
hmorgancode File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
The documentation suggests that
setup-node
can automatically cache what needs to be cached:The documentation for actions/setup-node suggests that simply adding
cache: true
will have similar effect, potentially caching the entirenode_modules
folder. So it seems like caching is a good idea, but I think it would be good to understand and measure the difference between just specifyingcache: true
tosetup-node
and separately configuringactions/cache
. And then the final choice should be documented with local comments so that if things change down the road the situation can be revisited.