鉂勶笍馃弫 Bootsnap Setup Convenience Require #81
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've been doing a lot of testing to get Bootsnap working correctly. A lot more work has happened to measure the tradeoffs when using Bootsnap's compilation caching and/or path pre-scanning. I'll share more data on this in Lamby guides or some dev.to posts. For now, this is a convenience require that I am sure will work no matter how the final production data measurements come out. Here too are some Bootsnap issues links too where I hope to work more with the Shopify & AWS teams to dial this in for Lambda & Rails.