-
Notifications
You must be signed in to change notification settings - Fork 132
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
switch Yarn v3 #4777
Closed
Closed
switch Yarn v3 #4777
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
- use 1.4 syntax to support `COPY --link` commands - set NODE_ENV=production - remove $WORK build arg
…ching - If e.g. `test` has been added in a command/step, removing it in a subsequent command/step does not have a positive effect on the image size. Rather, we add it .dockerignore to stop adding it in the first place. - node_modules/.cache & /tmp/Relay* are populated by Webpack plugins.
app/server.js reads .entrypoints.main.assets in order to generate an appropriate manifest and `preload` tags, but it doesn't need the rest. This is why we turn all stats off via `all: false` and then selectively turn `entrypoints` on. Before, stats.json was 82mb, now it is ~9kb.
Even if a commit has changed `yarn.lock`, we can use an old `.yarn/cache` directory, so that we don't have to fetch 99% of all dependencies again.
This reverts 32bbfa8, which reverts 3f6e105, which apparently failed because of an unrelated problem[1]. [1] https://github.com/HSLdevcom/digitransit-ui/actions/runs/4762670497/jobs/8469259999
This probably improves favicons-webpack-plugin's performance, as node_modules won't be resolved for resolving the path.
This speeds up the webpack build within the Docker image build significantly.
Co-Authored-By: Jannis R <[email protected]>
derhuerst
force-pushed
the
yarn-v3-upstream
branch
from
June 23, 2023 10:29
2ec23a8
to
584d7df
Compare
This PR got already merged into V3 as a part of #4838 . |
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.
This PR includes the changes of and depends on PR #4776; Please review & merge that one first.
Proposed Changes
-v3
to the cache keys, in order to prevent incompatible caches from being restoredyarn.lock
💥 (done via running justyarn
)Pull Request Check List
Review
(This is the upstream equivalent of embarkokc#22.)