You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally, the `makefile` serves as the de facto interface for project
scripts. This avoids multiple sources of truth and simplifies project
onboarding and documentation.
Previously, rerunning various `make` targets resulted in rerunning the
expensive and slow `make build` target. It's important to ensure the
build output exists for many targets, but is often unnecessary to rerun
the build when running targets multiple times--e.g., Swift test targets.
This introduces a caching mechanism. The `make build` target skips
running and relies upon the cache unless one of the following is true.
- dist doesn't exist
- REFRESH_JS_BUILD is set to true or 1
- build was invoked directly
This enables quicker reruns while also ensure the build is always
recreated when important to do so--e.g., direct invocations, CI runs,
releases.
See #253 (comment)
0 commit comments