-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
chore(gatsby): enable query on demand (and lazy images) by default for local development #28787
Conversation
…ures become defaults
… local development
process.env.PRESERVE_FILE_DOWNLOAD_CACHE = `true` | ||
process.env.PRESERVE_WEBPACK_CACHE = `true` |
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.
This is just "random" thing I spotted when looking for qod related changes I needed - we added those to FAST_DEV
config flag but not to GATSBY_EXPERIMENTAL_FAST_DEV
env var route - I can drop those from here, but it would be weird for FAST_DEV
to only map to DEV_SSR
🤷
if (message.length > 0) { | ||
message += `\n` | ||
} |
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.
This was sometimes causing \n
message without any text (yikes)
"message": " | ||
|
||
We're shipping new features! For final testing, we're rolling them out first to a small % of Gatsby users |
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.
Result of adding checks before appending newlines to message
in handle-flags.ts
- it should no longer have "ghost" empty lines in front of messages
…anymore - those are defaults
Co-authored-by: Vladimir Razuvaev <[email protected]>
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.
Nice! I tried it locally and it works as one would expect. Thanks! 👍
…r local development (gatsbyjs#28787) * feat(flags): add LOCKED_IN mode for flags for cases where opt-in features become defaults * feat(gatsby): enable query on demand (and lazy images) by default for local development * fix "lint" * chore(telemetry): don't track usage of query on demand / lazy images anymore - those are defaults * use plain false instead of weird Symbol do opt out of telemetry tracking * Update packages/gatsby/src/utils/handle-flags.ts Co-authored-by: Vladimir Razuvaev <[email protected]> * update snapshots Co-authored-by: Vladimir Razuvaev <[email protected]>
Description
This PR "graduates" query on demand mode to default in non-CI environment.
Main change here is adding support for
LOCKED_IN
setting for flags - this is done mainly to display more meaningful message in terminal. Removing the flag from the list would result in "unknown" flag message that could be confusing.