There is no flag --log-pages in my gatsby build command
See original GitHub issueSummary
at https://www.gatsbyjs.org/docs/page-build-optimizations-for-incremental-data-changes/#reporting-what-has-been-built it is writting I can use a --log-pages
flag. But my cli says that flag does not exist. I tried different recent versions of gatsby.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Debugging Incremental Builds | Gatsby
With the release of Gatsby v3 Incremental Builds is available to everyone. This improvement is (re)generating only subset of HTML files…
Read more >Improving your Gatsby build time by 300% - YouTube
Gatsby Incremental Builds promise to reduce your Gatsby application's build time down to 10 seconds – it's a big claim! Does Gatsby deliver?...
Read more >Gatsby Incremental Builds and Github Actions - Raul Melo
If you want to see what pages have been changed, you can pass the flag --log-pages at the end of the command. In...
Read more >Incremental builds not working as expected with Contentful
Our build command is currently prefaced with gatsby clean && . ... There doesn't seem to be a new deploy triggered in the...
Read more >reactjs - how to use incremental build in Gatsby feature ...
Note: the --log-pages flag will help you to identify the built pages on each run. To ensure a cross-environment command support I'd ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey folks. We just released
gatsby-cli@2.12.16
/gatsby@2.21.22
(thanks to PR by @albertlincoln ). Updating should fix this problemhttps://github.com/gatsbyjs/gatsby/pull/23839 yargs upgraded from v12 to v15 and is incompatible.