[www] add search input to home page #3662

m-allanson · 2018-01-23T12:21:56Z

This is here to start a discussion on adding search form onto the homepage.

I've removed the Discord and Twitter logos and added some inverse styling for the search icon.

@fk and @KyleAMathews what do you think, is this approach worth pursuing or should we try something else? The main downsides I can see are:

we've lost those two icons
the expanded search input overlaps the purple diagonals at some widths

Refs #3603 and particularly @fk's comment at #3097 (comment)

(This will probably need to be revisited once #3639 is in)

gatsbybot · 2018-01-23T12:28:00Z

Deploy preview for gatsbygram ready!

Built with commit d9604a2

https://deploy-preview-3662--gatsbygram.netlify.com

gatsbybot · 2018-01-23T12:33:43Z

Deploy preview for gatsbygram ready!

Built with commit 42c20b2

https://deploy-preview-3662--gatsbygram.netlify.com

KyleAMathews · 2018-01-23T18:39:12Z

I'm not super concerned about losing the icons. We should double-check analytics but I'd guess not a ton of people click on those links. Search feels like it's more important?

Also there's the community page with links to both of those.

KyleAMathews · 2018-01-23T18:40:23Z

Looking good though! https://deploy-preview-3662--gatsbyjs.netlify.com/

Maybe though the input background should be more muted when not focused? It feels overly contrasty / attention-grabbing right now.

m-allanson · 2018-01-23T21:18:58Z

Maybe though the input background should be more muted when not focused? It feels overly contrasty / attention-grabbing right now.

Yeah it's definitely bright atm, I'll take a look at muting it a bit.

m-allanson · 2018-01-23T21:21:15Z

Oh one of the AppVeyor builds failed.. does it just need a restart?

KyleAMathews · 2018-01-23T22:55:50Z

Appveyor is pretty unreliable. Looking at the build, there's what looks like an install error 🤷‍♂️

m-allanson · 2018-02-01T21:52:55Z

@KyleAMathews Alright, a few updates here:

prevent search input from overlapping bg stripes (home page)
mute colours of the unfocussed, expanded search input (home page)
add Twitter and Discord icons back in when there's enough space
rebase to include @fk's recent colour updates

KyleAMathews · 2018-02-01T22:50:20Z

Deploy preview for using-glamor failed.

Built with commit 42c20b2

https://app.netlify.com/sites/using-glamor/deploys/5a738ac8a6188f5aecbd0a0e

KyleAMathews · 2018-02-02T20:12:00Z

@m-allanson it looks like the input's background is still white when unfocused?

m-allanson · 2018-02-02T20:57:51Z

@KyleAMathews it should look like this:

I've just tried to trigger a rebuild on netlify.

KyleAMathews · 2018-02-02T22:47:55Z

Ugh ok sorry — yeah Netlify builds were broken because of the bad publish.

KyleAMathews · 2018-02-02T22:49:11Z

Looks great! Thanks for taking this on!

fk · 2018-02-03T14:16:25Z

❤️ 🙏 @m-allanson!

Special thanks for dealing with my messy color palette changes! 😉

m-allanson · 2018-02-03T18:02:19Z

🎉 🎉

@bodia-uz

* Revert "Update gatsby-browser.js (#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (#3717) * Publish - [email protected] * Add missing (official) plugins & little fixes (#3718) * Add missing (official) plugins & little fixes As talked about in: #3708 Fingers crossed that I didn't mess up the alphabetical order :P (I actually changed the order a little bit) * Add gatsby-source-graphcms * fix(transformer-remark): resolve htmlAst correctly (#3719) closes #3711 * Added my new websites to showcase (#3729) * Adjust default link header value in netlify plugin readme (#3723) * Change "primatives" to "primitives" in GraphQL docs (#3716) * [gatsby-transformer-remark] Reparse `raw` nodes in `htmlAst` (#3731) Preprocessing via `gatsby-remark-*` transformations introduces `raw` nodes into the AST. Adding this step fully enables the client to render the AST as React components, finishing the work started in #3596. * Publish - [email protected] - [email protected] - [email protected] - [email protected] * fix(gatsby-link): correct dependency declaration (#3707) * fix(gatsby-link): correct dependency declaration The code depends on `react-router-dom`, and therefore it should be declared as a direct dependency, not a dev one. Also, it needs `@types/react-router-dom` for index.d.ts. * chore(gatsby-link): declare gatsby v1 as a peer dependency * Publish - [email protected] - [email protected] * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (#3735) * Publish - [email protected] - [email protected] * Update CONTRIBUTING.md (#3737) incorrect usage of "it's" * Add freeCodeCamp source (#3739) * Add Hack Club to projects list (#3748) * Link title not particularly accurate * Fix link syntax (#3749) * add basic documentation about publicURL field on File node (#3752) * add basic documentation about copying files from File nodes to build directory * A few copy edits * Format * Format * [www] Fix link to "Adding Markdown Pages" in List docs (#3747) * [www] Add "gatsby-plugin-fela" to list of community plugins * Semi-Colons (#3764) * Remove mention of not-written part 5 of the tutorial * [www] Add ERC dEX website to showcase (#3766) * make ComponentRenderer shouldUpdateComponent return true when props c… (#3516) * make ComponentRenderer shouldUpdateComponent return true when props change * use shallow compare * remove console log * semi-colons (#3765) * [gatsby] Report an error when layout file is missing (#3762) * [gatsby] Report an error when layout file is missing * Update pages-writer.js * format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath (#3211) * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath * Update README.md * Add a no-color option to disable the colors (#3755) * disable boolean-negation in yargs * add no-color option * [www] Add gatsby-source-unsplash to list of community plugins (#3768) * format * Publish - [email protected] - [email protected] - [email protected] * Add setTimeout before calling onRouteUpdate to ensure React has written to DOM before plugins run code (#3772) * Improve errors for invalid data passed to createPage fixes #3771 (#3773) * Fix not scrolling to top on PUSH fixes #3770 #3249 (#3775) * [examples/using-remark]: Custom React components in Markdown files (#3732) * Publish - [email protected] - [email protected] - [email protected] - [email protected] * [www] Prevent search shortcut from breaking other input elements (#3777) * Edits from Ben's feedback * Logos * Delete React_logo_wordmark.png * Delete contentful_logo_with_tagline.png * logos * Added react and contentful logos * Update index.md * Delete React-logo.png * Delete contentful-logo.png * logos smaller * updated intro * Update index.md * [www] Add gatsby-plugin-sentry to list of community plugins (#3788) * [www] Add gatsby-plugin-meta-redirect to list of community plugins (#3798) * Form currently refreshes the page on pressing enter (#3779) * Added some notes on how the contentful source plugin interacts with contentful's content models. (#3794) * More hot reloading fixes (#3769) * use createPage singleton in dev-404-page closes #3551 * write to a temp file and rename decrease the chance of reading from an incomplete file cc #3094 #3201 * change dev-404-page to implement createPagesStatefully * update the jest snapshot * Validate starterPath isn't a dot fixes #3789 (#3810) * [gatsby] Pass location state to history (#3802) * Pass full location object to history * Update navigateTo param to be more precise * Pass location to navigateTo in gatsby-link * Update navigateTo types * Fix issue that Gatsby can't sometimes find layout and page files on Windows (#3796) * Fix issue with missing layouts on Windows * Fix issue with missing pages on Windows * Publish - [email protected] - [email protected] - [email protected] - [email protected] * Add iContract blog to readme (#3805) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` (#3801) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` The less plugin did its job, but when I was going to use it with a library I experienced that it was lacking the ability to modify less-variables. This made it hard to customize less libraries. By letting the user provide a `options` in `gatsby-config.js`, the plugin can overwrite variables defined in the less stylesheet and hence makes it a breeze to customize libraries. The user has two options to include vars: either a object defined directly in the `gatsby-config.js` or define a file which exports an object that will be used as the options. * Update README.md * format * Publish - [email protected] - [email protected] - [email protected] * Fix a typo in the gatsby-plugin-less README (#3815) * Call done() from dev-404-page during production builds so build doesn't stall (#3827) * Publish - [email protected] - [email protected] * Update README.md (#3828) * Added logos (#3781) * Added logos Not sure how to adjust the sizes here. I made them smaller on my computer but not sure if it worked * Reduce React and Contentful logo width to 350px * Log error in createPath (#3814) Fix conditional to show error when path or component are missing in the createPath function * add warning about query that is not getting executed if it's exported from file that is page/template or layout (#3786) * Update README.md (#3821) add module.exports to How to use * Update README.md * Added Hampton starter (#3826) * [www] add search input to home page (#3662) * Experiment adding search input to home page * Prettier * Comment unused imports * Display social icons when viewport is wide enough * Use alternate colours at Hd breakpoint on home page * Add name of file above code snippet (#3835) * [www] Fix typo in styleshout link (#3839) * Add "Dona Rita" website to Showcase (incl. source) (#3838) * check markdown images, ensure parent is File before referencing dir (#3831) * check markdown images, ensure parent is File before referencing dir * add check for parent * [www] Fix typo in docs/building-apps-with-gatsby.md (#3863) * Bump scroll-behavior dependency to fix ios swipe jank (#3866) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Fix positioning of search results at mobile breakpoint on homepage (#3867) * [www] Add tutorial to awesome list (#3855) This is the first part of a german tutorial series about Gatsby. This part is about the basic creation of a blog. In the next parts I'll cover more advanced features :) * [www] Update Netlify URL in Starter List (#3847) * Add gatsby-wordpress-starter (#3848) * exclude offline plugin app shell from sitemap (#3844) * [gatsby-source-contentful] Add support to prefer WebP images (#3832) * Extend contentful resolutions and sizes to include webp src and srcSet * Add new contentful fragments * Add fragments to gatsby-image README * Add example for using webp to use-contentful site * Display image examples in a grid * Update docs for adding custom JavaScript to home.js (#3869) * Blog post headless CMS (#3846) * Blog post headless CMS A couple things I'm not sure about: - Running sites offline paragraph. Check for accuracy pls! - Better quote from Deane that anyone has in mind? - Can cut down assessment of headless CMSs to omit obscure complaints... * Edits to wording and sprinkling in GatsbyJS Please check paragraph about running sites offline in India! I feel like there's potential there but maybe I'm off base * Update index.md * don't try to extract queries from directories with names ending in .js(x) or .ts (#3861) * Format * [gatsby-source-filesystem] don't try to process same remote file multiple times, cache promises and return them on subsequent calls (#3859) * Experimenting (#3843) * Update README.md (#3822) add module.exports to How to use * Format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Use HTTPS over git:// when cloning starters (#3820) `git://` (which is what `hostInfo.git(...)` gets you) uses unencrypted transport isn't recommended as a way to clone GitHub repositories (https://help.github.com/articles/which-remote-url-should-i-use/). This change uses HTTPS instead. * Add gatsby-transformer-screenshot (#3526) * Add gatsby-plugin-screenshot * Rename to gatsby-transformer-screenshot * Rename * Fix prepublish error * Expand on documentation * Run format-packages * Use API Gateway * Use official deployed Lambda * Update README.md * Format * Publish - [email protected] - [email protected] - [email protected] * [gatsby-plugin-feed] Fix missing colon in Readme (#3872) * Revert "Use HTTPS over git:// when cloning starters (#3820)" (#3876) This reverts commit 8261ac3. * Publish - [email protected] - [email protected] - [email protected] * use simple https to clone starters (#3875) * Publish - [email protected] - [email protected] * [www] Add gatsby-starter-simple-landing (#3877) * bigger photo * Update index.md * add www.aslezak.com to showcase (#3878) * Added new blog, new author and new avatar (#3879) * Added new blog, new author and new avatar * Fix links * Spelling issue corrected, wp file extension changed and quotes corrected * format blog post * Update index.md (#3883) * Add community source plugin to docs (#3884) * [www] Fix small typo (#3891) * Document all options for gatsby-remark-images fixes #3882 (#3894) * Document all options for gatsby-remark-images fixes #3882 * remove * Edits to wording * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ (#3887) * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ Ref. #3886 * Add headline for `PostLink` component * Add possessive adjective * Make code blocks jsx * Add anchors to h1's in docs (#3892) * Add anchors to h1's in docs * Manually add some anchors * exclude Netlify CMS styles in build-css phase (#3895) * Fix markdown table syntax in README (#3897) * Publish - [email protected] - [email protected] - [email protected] * Fix typo (#3899) * update prismjs-language-dependencies.js (#3898) * Publish - [email protected] - [email protected] * Update snapshots and packages and format w/ new Prettier (#3902) * Update snapshots and packages and format w/ new Prettier * Update snapshot in embed package * [gatsby-transformer-remark] Add `pathPrefix` to relative links (#3823) * [gatsby-transformer-remark] Add `pathPrefix` to relative links Ensure markdown relative links include `pathPrefix`. Fixes #3316 * [gatsby-transformer-remark] add minor comment to `withPathPrefix` * [gatsby-transformer-remark] add `pathPrefix` to `cacheKey` functions * [gatsby-transformer-remark] remove `node.url.startsWith(pathPrefix)` condition for `withPathPrefix` logic * Use "npm-run-all" to run scripts (#3797) * Use "npm-run-all" to run scripts [npm-run-all](https://github.com/mysticatea/npm-run-all) is a cross-browser approach to running npm tasks in series (`-s`) or parallel (`-p`). Rather than using a platform specific method to run scripts (e.g. `&&`), npm-run-all will work on all platforms and supports using Yarn if running with Yarn. I made a guess as to whether certain scripts should be run in series or parallel but feel free to change if my choices aren't optimal. * Add yarn.lock and fix some scripts. * Move npm-run-all to dev dep. * Fix bootstrap script. * [www] Starters: Fix case according to vendor name definition (#3903) * http://getbootstrap.com/ * http://postcss.org/ * https://sass-lang.com/ * https://bootswatch.com/ * Publish - [email protected] - [email protected] - [email protected] - [email protected] * add info about org-mode transformer plugin (#3907) I created this transformer plugin similar to the offical remark one, that parses org-mode files. * [www] add gatsby-orga starter (#3908) * update odayaka.net to showcase (#3909) update odayaka.net to showcase * [www] Add ventura-digital.de to Showcase (#3916) * Minor edits for absolute beginners After doing this tutorial as a complete beginner myself, I thought a couple of lines could be made even more newby-friendly. * Update tutorial.js (#3927) * ✨ Support filtering on linked nodes (#3691) * ✨ Support filtering on linked nodes The filtering is done by extracting all the related nodes using `extractFieldExample`. The example values are then cached to save some time. (As of this patch, caching is not tested automatically) Further linking are disabled to avoid cyclic dependencies (input fields only). TODO: Filtering on nodes linked by mappings and File Note: If linking is done via array of IDs, only the structure of the first item is extracted. I'll be happy to add union support if someone can show me how to `$in` filter on an array of object. Related #3613 #3190 * ✅ Test filtering on linked nodes * Publish - [email protected] * Set default NODE_ENV for `gatsby develop` (#3928) * Fix broken links (#3930) * Blog Post - Jam Out Your Blog (#3911) * Blog Post - Jam Out Your Blog Vlad Pasculescu’s blog post on using Gatsby with Netify and Prose.io Signed-off-by: vladpasculescu <[email protected]> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - [email protected] - [email protected] * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes (#3522) * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes Fixes: #3521 * refactor(dev-404-page): use RegExp.test() as we don't need to return anything * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes updating other occurrence of 404 page check as well * Automatic file validation for components in src/pages (#3881) * yarn.lock * add page validation and fix breaking createPage action tests * Improve error messages for invalid pages * Field inferring changes and cleanup (#3688) * remove not needed edge case for infering array of objects to improve code readability * don't lose field args and resolve function when infering array (fixes date format options not available in arrays of dates) * move infering date field to seperate file to improve code readability * don't recreate date field definition for every date field - we can reuse same object * create dedicated Date graphql scalar (based on string scalar) for date fields * pass fieldName to resolver when filtering on types with custom resolvers (date type fields now rely on fieldname info being passed) * use already constructed nextselector instead of rebuilding it again * move infering file field to separate file to improve code readability * create file type field object just once and reuse it * move trying to infer Files from string paths to inferGraphQLType function where rest of value based inferring is done * add tests for inferring File from string paths * add tests for inferring date type from string, array of strings and filtering date fields, move date related test to seperate date test suite * Publish - [email protected] * Return a never to be resolved promise to prevent development server from exiting early fixes #3932 (#3933) * Publish - [email protected] - [email protected] * format * Add Cardiogram to README (#3934) * Fix code highlight in tutorial (#3935) * small wording change * [api-ssr-docs] Import `Helmet` not `helmet` (#3940) * [www] Tutorial: Small wording changes for clarification (#3926) gatsby-config.js needs to be created (before edited). Also, since the user will be changing windows to stop the process it might be useful to remind them where they were before. * [docs] Fix small typo (#3946) * test "exports.default" when validating page component (#3941) * Publish - [email protected] * update environment variables docs to explain how to implement dotenv (#3944) * [www] Add dedicated „How to File an Issue“ page (#3945) * move „Filing an Issue“ and „Special Note on Issues“ from the „How to Contribute“ to the new „How to File an Issue“ page * add an intro paragraph to the new page linking to the GitHub Gatsby issue tracker * add a paragraph to the new page informing about personal support requests, pointing to Stack Overflow, Reactiflux Discord * add link to the new page to * the docs sidebar’s „Contributing“ section * the GitHub issue template * the „Community“ page * the list of ways to contribute on the „How to Contribute“ page * link „Triaging GitHub issues“ on the „How to Contribute“ page * Don't check if React is imported as can import component from other page and never write JSX (#3949) /cc @bodia-uz * Publish - [email protected] * Add LaserTime Clinic website to Readme (#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (#3952) * Publish - [email protected] * type inferring - handle array of Date objects (#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - [email protected] * Document how to create custom fragments (#3914) * Document how to create custom fragments * Fix ordering * Add example component exporting a fragment * Tweak language * Update index.md (#3957) * update showcase with Gatsby Manor (#3959) Gatsby Manor makes themes for GatsbyJS. * Adds new starter to docs :) (#3971) * Fix error (#3985) Talked to Ross Whitehouse, the author, via Medium private message to confirm the errors. Gotten permission to submit PR for the edit. * Add note about plugin options (#3987) * Add container as a styled div to styled-components doc (#3988) * Add Dockerfile to start GraphiQL using www's data (#3992) * fix: prevent invalid graphql field names from being created (#3994) * fix: prevent invalid graphql field names from being created Note: This will currently transform (for example) `/*` into `_` so I'm not quite sure what the best course of action is to replace that Fixes #3487; Fixes #2925 * chore: revert yarn lock change * test: simplify tests * fix: dasherize after leading underscore * feat(gatsby-plugin-google-analytics): add head option (#3995) Add head option to configure whether scrip tag should be put in the body (by default, same as previously) or inside of the head. closes #2894 * Add browserAPIs and ssrAPIs to loaded plugin info (#3989) * Add browserAPIs and ssrAPIs to loaded plugin info * Output correct error message for each bad export * Use lodash for Node 6 compatibility * Publish - [email protected] - [email protected] * add package json metadata for better display on npmjs.org (#3981) * chore: add package json metadata (git url, issues, etc.) * chore: update plop template * chore: move bin/files up in package.json * chore: fix unescaped email(s) * Run 'fixpack' on all package.jsons * Validate when creating a page that the page component exists (#3997) * Validate when creating a page that the page component exists * Don't check for component paths during testing as it breaks tests * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-transformer-react-docgen] Add note on PropTypes (#4008) * Update adding-tags-and-categories-to-blog-posts.md (#3999) Changed per a conversation with Kyle about a better way to do this. Relates to #3976 * [gatsby-remark-katex] Upgrade remark-math to latest (#4005) * update remark-math to latest version to fix an issue where equations surrounded by `$$` with new lines are not displayed in KaTeX' `displayMode` * update broken spec * add spec for display math node * [using-remark] fix "Math Equations in Display Mode" example * Add note about using Custom Domain with Github Pages (#4006) * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * [docs] Add Gatsby Manor blog post (#3968) Show the community Gatsby Manor. * don't use internal-only path when requiring promise polyfill (#4012) see: zloirock/core-js#138 (comment) * Fix tracking parent nodes when loading redux state from cache (#4013) fixes #2929 * Publish - [email protected] - [email protected] - [email protected] * Add info about gatsby-plugin-sharp (#4019) * Add info about gatsby-plugin-sharp * Update README.md * update contributing documentation to mention that npm run watch can be resource intensive, and suggest watching select packages at a time (#4020) * [gatsby-image] Allow specifying HTML tag for gatsby-image wrapping elements (#4022) * Allow specifying which html tag will be used for gatsby-image wrappers * Update gatsby-image README.md to include new Tag prop * Fix plugin loader checks (#4023) * Add browser and SSR APIs to the plugin API whitelist * Add registerServiceWorker to the list of allowed browser APIs * Publish - [email protected] - [email protected] * Fix tracking nodes with filtering/running sift (#4024) * Track Node that contains inline objects/arrays instead of its parent. This doesn't break finding topmost ancestor node as we already trying to get walk along parent hierarchy. Rename tracking functions and jsdocs to provide some basic context for these functions * Fix tracking nodes with filtering/running sift. Before we filter nodes we create copies of nodes with appended fields added by plugins (by setFieldsOnGraphQLNodeType) if they are filtered on. These copies weren't tracked. * fix: add info message if gatsby-config.js could have been typo'd (#4017) * fix: add info message if gatsby-config.js could have been typo'd * chore: move preferDefault back to where it was * refactor: tweak error logic a bit * chore: tweak versions for yarn.lock compat * refactor: address PR comments * fix: fail with error * format * Fix lint errors * fix: ensure graphql key is a valid graphql key value (#4000) * fix: ensure graphql key is a valid graphql key value * chore: update comment * Improve the warning for when someone includes a graphql query in a non-page component (#4026) * Publish - [email protected] * add gatsby-transformer-javascript-frontmatter, closes #3795 (#3947) * initial commit * update name in package.json * start converting example site * fix gql error on js articles * rename intial defined `let` * clear out unused deps * begin updating new layout components * fix all HOC * update example readme * Format * Update README.md * Catch require error for hot-reloading gatsby-config.js fixes #3990 (#4039) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Don't exit on errors as during development, empty/incomplete page components are common fixes #4027 (#4040) * Don't exit on errors as during development, empty/incomplete page components are common fixes #4027 * Fix other points of death * Ok, do die here * Remove component query from store when a user deletes it fixes #4032 (#4041) * Publish - [email protected] * add portfolio site to the readme showcase (#4043) * Add documentation for using boundActionCreators fixes #4029 (#4042) * Add documentation for using boundActionCreators * Update bound-action-creators.js * Fix * node tracking - add tests (#4045) * move node tracking code to separate dedicated file * Add jsdoc for findRootNode * add tests for node tracking * Update README.md * Add links to the end of the tutorial (#4051) * [www] Fix tutorial sidebar links active state, update deps (#4059) * Bump deps, add react-helmet for gatsby-plugin-react-helmet v2 * Fix warning „Warning: Received `false` for non-boolean attribute `className`. If this is expected, cast the value to a string.“ * Update preload href * Rewire sidebar section and link styles, fix #4036 * Use babylon to parse out exports from plugin files (#4057) * Fixes * Fix package.json * Fix package.json * Ignore tests * Fix lint * Comment out less tests until theme functionality can be ported to v2

@bodia-uz

* Revert "Update gatsby-browser.js (#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (#3717) * Publish - [email protected] * Add missing (official) plugins & little fixes (#3718) * Add missing (official) plugins & little fixes As talked about in: #3708 Fingers crossed that I didn't mess up the alphabetical order :P (I actually changed the order a little bit) * Add gatsby-source-graphcms * fix(transformer-remark): resolve htmlAst correctly (#3719) closes #3711 * Added my new websites to showcase (#3729) * Adjust default link header value in netlify plugin readme (#3723) * Change "primatives" to "primitives" in GraphQL docs (#3716) * [gatsby-transformer-remark] Reparse `raw` nodes in `htmlAst` (#3731) Preprocessing via `gatsby-remark-*` transformations introduces `raw` nodes into the AST. Adding this step fully enables the client to render the AST as React components, finishing the work started in #3596. * Publish - [email protected] - [email protected] - [email protected] - [email protected] * fix(gatsby-link): correct dependency declaration (#3707) * fix(gatsby-link): correct dependency declaration The code depends on `react-router-dom`, and therefore it should be declared as a direct dependency, not a dev one. Also, it needs `@types/react-router-dom` for index.d.ts. * chore(gatsby-link): declare gatsby v1 as a peer dependency * Publish - [email protected] - [email protected] * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (#3735) * Publish - [email protected] - [email protected] * Update CONTRIBUTING.md (#3737) incorrect usage of "it's" * Add freeCodeCamp source (#3739) * Add Hack Club to projects list (#3748) * Link title not particularly accurate * Fix link syntax (#3749) * add basic documentation about publicURL field on File node (#3752) * add basic documentation about copying files from File nodes to build directory * A few copy edits * Format * Format * [www] Fix link to "Adding Markdown Pages" in List docs (#3747) * [www] Add "gatsby-plugin-fela" to list of community plugins * Semi-Colons (#3764) * Remove mention of not-written part 5 of the tutorial * [www] Add ERC dEX website to showcase (#3766) * make ComponentRenderer shouldUpdateComponent return true when props c… (#3516) * make ComponentRenderer shouldUpdateComponent return true when props change * use shallow compare * remove console log * semi-colons (#3765) * [gatsby] Report an error when layout file is missing (#3762) * [gatsby] Report an error when layout file is missing * Update pages-writer.js * format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath (#3211) * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath * Update README.md * Add a no-color option to disable the colors (#3755) * disable boolean-negation in yargs * add no-color option * [www] Add gatsby-source-unsplash to list of community plugins (#3768) * format * Publish - [email protected] - [email protected] - [email protected] * Add setTimeout before calling onRouteUpdate to ensure React has written to DOM before plugins run code (#3772) * Improve errors for invalid data passed to createPage fixes #3771 (#3773) * Fix not scrolling to top on PUSH fixes #3770 #3249 (#3775) * [examples/using-remark]: Custom React components in Markdown files (#3732) * Publish - [email protected] - [email protected] - [email protected] - [email protected] * [www] Prevent search shortcut from breaking other input elements (#3777) * Edits from Ben's feedback * Logos * Delete React_logo_wordmark.png * Delete contentful_logo_with_tagline.png * logos * Added react and contentful logos * Update index.md * Delete React-logo.png * Delete contentful-logo.png * logos smaller * updated intro * Update index.md * [www] Add gatsby-plugin-sentry to list of community plugins (#3788) * [www] Add gatsby-plugin-meta-redirect to list of community plugins (#3798) * Form currently refreshes the page on pressing enter (#3779) * Added some notes on how the contentful source plugin interacts with contentful's content models. (#3794) * More hot reloading fixes (#3769) * use createPage singleton in dev-404-page closes #3551 * write to a temp file and rename decrease the chance of reading from an incomplete file cc #3094 #3201 * change dev-404-page to implement createPagesStatefully * update the jest snapshot * Validate starterPath isn't a dot fixes #3789 (#3810) * [gatsby] Pass location state to history (#3802) * Pass full location object to history * Update navigateTo param to be more precise * Pass location to navigateTo in gatsby-link * Update navigateTo types * Fix issue that Gatsby can't sometimes find layout and page files on Windows (#3796) * Fix issue with missing layouts on Windows * Fix issue with missing pages on Windows * Publish - [email protected] - [email protected] - [email protected] - [email protected] * Add iContract blog to readme (#3805) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` (#3801) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` The less plugin did its job, but when I was going to use it with a library I experienced that it was lacking the ability to modify less-variables. This made it hard to customize less libraries. By letting the user provide a `options` in `gatsby-config.js`, the plugin can overwrite variables defined in the less stylesheet and hence makes it a breeze to customize libraries. The user has two options to include vars: either a object defined directly in the `gatsby-config.js` or define a file which exports an object that will be used as the options. * Update README.md * format * Publish - [email protected] - [email protected] - [email protected] * Fix a typo in the gatsby-plugin-less README (#3815) * Call done() from dev-404-page during production builds so build doesn't stall (#3827) * Publish - [email protected] - [email protected] * Update README.md (#3828) * Added logos (#3781) * Added logos Not sure how to adjust the sizes here. I made them smaller on my computer but not sure if it worked * Reduce React and Contentful logo width to 350px * Log error in createPath (#3814) Fix conditional to show error when path or component are missing in the createPath function * add warning about query that is not getting executed if it's exported from file that is page/template or layout (#3786) * Update README.md (#3821) add module.exports to How to use * Update README.md * Added Hampton starter (#3826) * [www] add search input to home page (#3662) * Experiment adding search input to home page * Prettier * Comment unused imports * Display social icons when viewport is wide enough * Use alternate colours at Hd breakpoint on home page * Add name of file above code snippet (#3835) * [www] Fix typo in styleshout link (#3839) * Add "Dona Rita" website to Showcase (incl. source) (#3838) * check markdown images, ensure parent is File before referencing dir (#3831) * check markdown images, ensure parent is File before referencing dir * add check for parent * [www] Fix typo in docs/building-apps-with-gatsby.md (#3863) * Bump scroll-behavior dependency to fix ios swipe jank (#3866) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Fix positioning of search results at mobile breakpoint on homepage (#3867) * [www] Add tutorial to awesome list (#3855) This is the first part of a german tutorial series about Gatsby. This part is about the basic creation of a blog. In the next parts I'll cover more advanced features :) * [www] Update Netlify URL in Starter List (#3847) * Add gatsby-wordpress-starter (#3848) * exclude offline plugin app shell from sitemap (#3844) * [gatsby-source-contentful] Add support to prefer WebP images (#3832) * Extend contentful resolutions and sizes to include webp src and srcSet * Add new contentful fragments * Add fragments to gatsby-image README * Add example for using webp to use-contentful site * Display image examples in a grid * Update docs for adding custom JavaScript to home.js (#3869) * Blog post headless CMS (#3846) * Blog post headless CMS A couple things I'm not sure about: - Running sites offline paragraph. Check for accuracy pls! - Better quote from Deane that anyone has in mind? - Can cut down assessment of headless CMSs to omit obscure complaints... * Edits to wording and sprinkling in GatsbyJS Please check paragraph about running sites offline in India! I feel like there's potential there but maybe I'm off base * Update index.md * don't try to extract queries from directories with names ending in .js(x) or .ts (#3861) * Format * [gatsby-source-filesystem] don't try to process same remote file multiple times, cache promises and return them on subsequent calls (#3859) * Experimenting (#3843) * Update README.md (#3822) add module.exports to How to use * Format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Use HTTPS over git:// when cloning starters (#3820) `git://` (which is what `hostInfo.git(...)` gets you) uses unencrypted transport isn't recommended as a way to clone GitHub repositories (https://help.github.com/articles/which-remote-url-should-i-use/). This change uses HTTPS instead. * Add gatsby-transformer-screenshot (#3526) * Add gatsby-plugin-screenshot * Rename to gatsby-transformer-screenshot * Rename * Fix prepublish error * Expand on documentation * Run format-packages * Use API Gateway * Use official deployed Lambda * Update README.md * Format * Publish - [email protected] - [email protected] - [email protected] * [gatsby-plugin-feed] Fix missing colon in Readme (#3872) * Revert "Use HTTPS over git:// when cloning starters (#3820)" (#3876) This reverts commit 8261ac3. * Publish - [email protected] - [email protected] - [email protected] * use simple https to clone starters (#3875) * Publish - [email protected] - [email protected] * [www] Add gatsby-starter-simple-landing (#3877) * bigger photo * Update index.md * add www.aslezak.com to showcase (#3878) * Added new blog, new author and new avatar (#3879) * Added new blog, new author and new avatar * Fix links * Spelling issue corrected, wp file extension changed and quotes corrected * format blog post * Update index.md (#3883) * Add community source plugin to docs (#3884) * [www] Fix small typo (#3891) * Document all options for gatsby-remark-images fixes #3882 (#3894) * Document all options for gatsby-remark-images fixes #3882 * remove * Edits to wording * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ (#3887) * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ Ref. #3886 * Add headline for `PostLink` component * Add possessive adjective * Make code blocks jsx * Add anchors to h1's in docs (#3892) * Add anchors to h1's in docs * Manually add some anchors * exclude Netlify CMS styles in build-css phase (#3895) * Fix markdown table syntax in README (#3897) * Publish - [email protected] - [email protected] - [email protected] * Fix typo (#3899) * update prismjs-language-dependencies.js (#3898) * Publish - [email protected] - [email protected] * Update snapshots and packages and format w/ new Prettier (#3902) * Update snapshots and packages and format w/ new Prettier * Update snapshot in embed package * [gatsby-transformer-remark] Add `pathPrefix` to relative links (#3823) * [gatsby-transformer-remark] Add `pathPrefix` to relative links Ensure markdown relative links include `pathPrefix`. Fixes #3316 * [gatsby-transformer-remark] add minor comment to `withPathPrefix` * [gatsby-transformer-remark] add `pathPrefix` to `cacheKey` functions * [gatsby-transformer-remark] remove `node.url.startsWith(pathPrefix)` condition for `withPathPrefix` logic * Use "npm-run-all" to run scripts (#3797) * Use "npm-run-all" to run scripts [npm-run-all](https://github.com/mysticatea/npm-run-all) is a cross-browser approach to running npm tasks in series (`-s`) or parallel (`-p`). Rather than using a platform specific method to run scripts (e.g. `&&`), npm-run-all will work on all platforms and supports using Yarn if running with Yarn. I made a guess as to whether certain scripts should be run in series or parallel but feel free to change if my choices aren't optimal. * Add yarn.lock and fix some scripts. * Move npm-run-all to dev dep. * Fix bootstrap script. * [www] Starters: Fix case according to vendor name definition (#3903) * http://getbootstrap.com/ * http://postcss.org/ * https://sass-lang.com/ * https://bootswatch.com/ * Publish - [email protected] - [email protected] - [email protected] - [email protected] * add info about org-mode transformer plugin (#3907) I created this transformer plugin similar to the offical remark one, that parses org-mode files. * [www] add gatsby-orga starter (#3908) * update odayaka.net to showcase (#3909) update odayaka.net to showcase * [www] Add ventura-digital.de to Showcase (#3916) * Minor edits for absolute beginners After doing this tutorial as a complete beginner myself, I thought a couple of lines could be made even more newby-friendly. * Update tutorial.js (#3927) * ✨ Support filtering on linked nodes (#3691) * ✨ Support filtering on linked nodes The filtering is done by extracting all the related nodes using `extractFieldExample`. The example values are then cached to save some time. (As of this patch, caching is not tested automatically) Further linking are disabled to avoid cyclic dependencies (input fields only). TODO: Filtering on nodes linked by mappings and File Note: If linking is done via array of IDs, only the structure of the first item is extracted. I'll be happy to add union support if someone can show me how to `$in` filter on an array of object. Related #3613 #3190 * ✅ Test filtering on linked nodes * Publish - [email protected] * Set default NODE_ENV for `gatsby develop` (#3928) * Fix broken links (#3930) * Blog Post - Jam Out Your Blog (#3911) * Blog Post - Jam Out Your Blog Vlad Pasculescu’s blog post on using Gatsby with Netify and Prose.io Signed-off-by: vladpasculescu <[email protected]> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - [email protected] - [email protected] * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes (#3522) * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes Fixes: #3521 * refactor(dev-404-page): use RegExp.test() as we don't need to return anything * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes updating other occurrence of 404 page check as well * Automatic file validation for components in src/pages (#3881) * yarn.lock * add page validation and fix breaking createPage action tests * Improve error messages for invalid pages * Field inferring changes and cleanup (#3688) * remove not needed edge case for infering array of objects to improve code readability * don't lose field args and resolve function when infering array (fixes date format options not available in arrays of dates) * move infering date field to seperate file to improve code readability * don't recreate date field definition for every date field - we can reuse same object * create dedicated Date graphql scalar (based on string scalar) for date fields * pass fieldName to resolver when filtering on types with custom resolvers (date type fields now rely on fieldname info being passed) * use already constructed nextselector instead of rebuilding it again * move infering file field to separate file to improve code readability * create file type field object just once and reuse it * move trying to infer Files from string paths to inferGraphQLType function where rest of value based inferring is done * add tests for inferring File from string paths * add tests for inferring date type from string, array of strings and filtering date fields, move date related test to seperate date test suite * Publish - [email protected] * Return a never to be resolved promise to prevent development server from exiting early fixes #3932 (#3933) * Publish - [email protected] - [email protected] * format * Add Cardiogram to README (#3934) * Fix code highlight in tutorial (#3935) * small wording change * [api-ssr-docs] Import `Helmet` not `helmet` (#3940) * [www] Tutorial: Small wording changes for clarification (#3926) gatsby-config.js needs to be created (before edited). Also, since the user will be changing windows to stop the process it might be useful to remind them where they were before. * [docs] Fix small typo (#3946) * test "exports.default" when validating page component (#3941) * Publish - [email protected] * update environment variables docs to explain how to implement dotenv (#3944) * [www] Add dedicated „How to File an Issue“ page (#3945) * move „Filing an Issue“ and „Special Note on Issues“ from the „How to Contribute“ to the new „How to File an Issue“ page * add an intro paragraph to the new page linking to the GitHub Gatsby issue tracker * add a paragraph to the new page informing about personal support requests, pointing to Stack Overflow, Reactiflux Discord * add link to the new page to * the docs sidebar’s „Contributing“ section * the GitHub issue template * the „Community“ page * the list of ways to contribute on the „How to Contribute“ page * link „Triaging GitHub issues“ on the „How to Contribute“ page * Don't check if React is imported as can import component from other page and never write JSX (#3949) /cc @bodia-uz * Publish - [email protected] * Add LaserTime Clinic website to Readme (#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (#3952) * Publish - [email protected] * type inferring - handle array of Date objects (#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - [email protected] * Document how to create custom fragments (#3914) * Document how to create custom fragments * Fix ordering * Add example component exporting a fragment * Tweak language * Update index.md (#3957) * update showcase with Gatsby Manor (#3959) Gatsby Manor makes themes for GatsbyJS. * Adds new starter to docs :) (#3971) * Fix error (#3985) Talked to Ross Whitehouse, the author, via Medium private message to confirm the errors. Gotten permission to submit PR for the edit. * Add note about plugin options (#3987) * Add container as a styled div to styled-components doc (#3988) * Add Dockerfile to start GraphiQL using www's data (#3992) * fix: prevent invalid graphql field names from being created (#3994) * fix: prevent invalid graphql field names from being created Note: This will currently transform (for example) `/*` into `_` so I'm not quite sure what the best course of action is to replace that Fixes #3487; Fixes #2925 * chore: revert yarn lock change * test: simplify tests * fix: dasherize after leading underscore * feat(gatsby-plugin-google-analytics): add head option (#3995) Add head option to configure whether scrip tag should be put in the body (by default, same as previously) or inside of the head. closes #2894 * Add browserAPIs and ssrAPIs to loaded plugin info (#3989) * Add browserAPIs and ssrAPIs to loaded plugin info * Output correct error message for each bad export * Use lodash for Node 6 compatibility * Publish - [email protected] - [email protected] * add package json metadata for better display on npmjs.org (#3981) * chore: add package json metadata (git url, issues, etc.) * chore: update plop template * chore: move bin/files up in package.json * chore: fix unescaped email(s) * Run 'fixpack' on all package.jsons * Validate when creating a page that the page component exists (#3997) * Validate when creating a page that the page component exists * Don't check for component paths during testing as it breaks tests * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-transformer-react-docgen] Add note on PropTypes (#4008) * Update adding-tags-and-categories-to-blog-posts.md (#3999) Changed per a conversation with Kyle about a better way to do this. Relates to #3976 * [gatsby-remark-katex] Upgrade remark-math to latest (#4005) * update remark-math to latest version to fix an issue where equations surrounded by `$$` with new lines are not displayed in KaTeX' `displayMode` * update broken spec * add spec for display math node * [using-remark] fix "Math Equations in Display Mode" example * Add note about using Custom Domain with Github Pages (#4006) * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * [docs] Add Gatsby Manor blog post (#3968) Show the community Gatsby Manor. * don't use internal-only path when requiring promise polyfill (#4012) see: zloirock/core-js#138 (comment) * Fix tracking parent nodes when loading redux state from cache (#4013) fixes #2929 * Publish - [email protected] - [email protected] - [email protected] * Add info about gatsby-plugin-sharp (#4019) * Add info about gatsby-plugin-sharp * Update README.md * update contributing documentation to mention that npm run watch can be resource intensive, and suggest watching select packages at a time (#4020) * [gatsby-image] Allow specifying HTML tag for gatsby-image wrapping elements (#4022) * Allow specifying which html tag will be used for gatsby-image wrappers * Update gatsby-image README.md to include new Tag prop * Fix plugin loader checks (#4023) * Add browser and SSR APIs to the plugin API whitelist * Add registerServiceWorker to the list of allowed browser APIs * Publish - [email protected] - [email protected] * Fix tracking nodes with filtering/running sift (#4024) * Track Node that contains inline objects/arrays instead of its parent. This doesn't break finding topmost ancestor node as we already trying to get walk along parent hierarchy. Rename tracking functions and jsdocs to provide some basic context for these functions * Fix tracking nodes with filtering/running sift. Before we filter nodes we create copies of nodes with appended fields added by plugins (by setFieldsOnGraphQLNodeType) if they are filtered on. These copies weren't tracked. * fix: add info message if gatsby-config.js could have been typo'd (#4017) * fix: add info message if gatsby-config.js could have been typo'd * chore: move preferDefault back to where it was * refactor: tweak error logic a bit * chore: tweak versions for yarn.lock compat * refactor: address PR comments * fix: fail with error * format * Fix lint errors * fix: ensure graphql key is a valid graphql key value (#4000) * fix: ensure graphql key is a valid graphql key value * chore: update comment * Improve the warning for when someone includes a graphql query in a non-page component (#4026) * Publish - [email protected] * add gatsby-transformer-javascript-frontmatter, closes #3795 (#3947) * initial commit * update name in package.json * start converting example site * fix gql error on js articles * rename intial defined `let` * clear out unused deps * begin updating new layout components * fix all HOC * update example readme * Format * Update README.md * Catch require error for hot-reloading gatsby-config.js fixes #3990 (#4039) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Don't exit on errors as during development, empty/incomplete page components are common fixes #4027 (#4040) * Don't exit on errors as during development, empty/incomplete page components are common fixes #4027 * Fix other points of death * Ok, do die here * Remove component query from store when a user deletes it fixes #4032 (#4041) * Publish - [email protected] * add portfolio site to the readme showcase (#4043) * Add documentation for using boundActionCreators fixes #4029 (#4042) * Add documentation for using boundActionCreators * Update bound-action-creators.js * Fix * node tracking - add tests (#4045) * move node tracking code to separate dedicated file * Add jsdoc for findRootNode * add tests for node tracking * Update README.md * Add links to the end of the tutorial (#4051) * [www] Fix tutorial sidebar links active state, update deps (#4059) * Bump deps, add react-helmet for gatsby-plugin-react-helmet v2 * Fix warning „Warning: Received `false` for non-boolean attribute `className`. If this is expected, cast the value to a string.“ * Update preload href * Rewire sidebar section and link styles, fix #4036 * Use babylon to parse out exports from plugin files (#4057) * Minor typo fix (#4063) * sort type names when creating union type name to keep union type names more consistent (#4074) previously this name would change when order of source data change * Publish - [email protected] - [email protected] * Update minimum Node.js versions (#4075) * support tiff images and don't get stuck indefinitely when used, add basic error checking (#4076) * Remove .travis.yml file from www directory as it's never been used (#4082) * [www] Tutorial: Highlight closing tag (#3925) * Highlight closing tag There are two additions to the code, however only the opening div is highlighted and not its closing tag. * Made changes suggested by Yisela @yisela, I changed this! It took a while for me to figure out, which means that most beginners would also have trouble figuring it out, haha. Thanks for noticing and helping Gatsby improve!!! * Revert "define webpack loader.exclude with array for extensibility" (#4046) This reverts commit 50b0a47. * Add documentation for mapping in gatsby-config (#4054) * Add documentation for mapping * Fix glitch in pasted code * Update gatsby-config.md * format * Update gatsby-config.md * Update gatsby-config.md * Add new Tools-section and mention Gatsby-Docker (#4085) As suggested here: https://twitter.com/gatsbyjs/status/964531323606986752 * Remove ReasonML site (#4084) * Added gatsby-source-dribbble plugin (#4086) Added gatsby-source-dribbble plugin to community plugins * Adds add'l docs to gatsby-source-filesystem (#4060) * Adds add'l docs to gatsby-source-filesystem * Update README.md * Format * [docs] Add A Bright Future For The Web blog post (#4073) * Blogpost (#4083) * Blogpost Hope this is good to go. I feel like it's kind of boring and abstract. Hoped to have more examples or stories or screenshots but don't know enough to add more! * Update index.md Removed some content which felt a bit extraneous + corrected a few descriptions of React * Add portfolio of Preston Richey to README showcase (#4087) * gatsby.org -> gatsbyjs.org (#4088) * gatsby.org -> gatsbyjs.org * Update index.md * fix broken `path` dependency (#4090) Following the guide I had an error with the `path`. It seems that requiring it at the top of the file solves the issue: `const path = require("path");` Is there something else I was missing? Cheers * Remove tiff option from gatsby-plugin-sharp as it's converting all images to tiff (#4091) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [www] Fix quotes, fixes „Invalid date“ of latest blog post (#4092) * [www] Fix quotes, fixes „Invalid date“ of latest blog post * Fix typo * Auto-deploy GraphQL docker image (#4079) * Push image to docker hub when master is tagged like `gatsby@` * Build image on any commit to master (that isn't a PR merge) * Restore tiff option but without force option defaulting to true (#4094) * Publish - [email protected] - [email protected] * Add Beach Hut Poole to Site Showcase (#4106) * Add gatsby-starter-redux to gatsby-starters (#4098) * Catch and exit if someone mistakenly puts their gatsby-config.js in the src directory fixes #2674 (#4101) * Publish - [email protected]

@bodia-uz

* Revert "Update gatsby-browser.js (gatsbyjs#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (gatsbyjs#3717) * Publish - [email protected] * Add missing (official) plugins & little fixes (gatsbyjs#3718) * Add missing (official) plugins & little fixes As talked about in: gatsbyjs#3708 Fingers crossed that I didn't mess up the alphabetical order :P (I actually changed the order a little bit) * Add gatsby-source-graphcms * fix(transformer-remark): resolve htmlAst correctly (gatsbyjs#3719) closes gatsbyjs#3711 * Added my new websites to showcase (gatsbyjs#3729) * Adjust default link header value in netlify plugin readme (gatsbyjs#3723) * Change "primatives" to "primitives" in GraphQL docs (gatsbyjs#3716) * [gatsby-transformer-remark] Reparse `raw` nodes in `htmlAst` (gatsbyjs#3731) Preprocessing via `gatsby-remark-*` transformations introduces `raw` nodes into the AST. Adding this step fully enables the client to render the AST as React components, finishing the work started in gatsbyjs#3596. * Publish - [email protected] - [email protected] - [email protected] - [email protected] * fix(gatsby-link): correct dependency declaration (gatsbyjs#3707) * fix(gatsby-link): correct dependency declaration The code depends on `react-router-dom`, and therefore it should be declared as a direct dependency, not a dev one. Also, it needs `@types/react-router-dom` for index.d.ts. * chore(gatsby-link): declare gatsby v1 as a peer dependency * Publish - [email protected] - [email protected] * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (gatsbyjs#3735) * Publish - [email protected] - [email protected] * Update CONTRIBUTING.md (gatsbyjs#3737) incorrect usage of "it's" * Add freeCodeCamp source (gatsbyjs#3739) * Add Hack Club to projects list (gatsbyjs#3748) * Link title not particularly accurate * Fix link syntax (gatsbyjs#3749) * add basic documentation about publicURL field on File node (gatsbyjs#3752) * add basic documentation about copying files from File nodes to build directory * A few copy edits * Format * Format * [www] Fix link to "Adding Markdown Pages" in List docs (gatsbyjs#3747) * [www] Add "gatsby-plugin-fela" to list of community plugins * Semi-Colons (gatsbyjs#3764) * Remove mention of not-written part 5 of the tutorial * [www] Add ERC dEX website to showcase (gatsbyjs#3766) * make ComponentRenderer shouldUpdateComponent return true when props c… (gatsbyjs#3516) * make ComponentRenderer shouldUpdateComponent return true when props change * use shallow compare * remove console log * semi-colons (gatsbyjs#3765) * [gatsby] Report an error when layout file is missing (gatsbyjs#3762) * [gatsby] Report an error when layout file is missing * Update pages-writer.js * format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath (gatsbyjs#3211) * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath * Update README.md * Add a no-color option to disable the colors (gatsbyjs#3755) * disable boolean-negation in yargs * add no-color option * [www] Add gatsby-source-unsplash to list of community plugins (gatsbyjs#3768) * format * Publish - [email protected] - [email protected] - [email protected] * Add setTimeout before calling onRouteUpdate to ensure React has written to DOM before plugins run code (gatsbyjs#3772) * Improve errors for invalid data passed to createPage fixes gatsbyjs#3771 (gatsbyjs#3773) * Fix not scrolling to top on PUSH fixes gatsbyjs#3770 gatsbyjs#3249 (gatsbyjs#3775) * [examples/using-remark]: Custom React components in Markdown files (gatsbyjs#3732) * Publish - [email protected] - [email protected] - [email protected] - [email protected] * [www] Prevent search shortcut from breaking other input elements (gatsbyjs#3777) * Edits from Ben's feedback * Logos * Delete React_logo_wordmark.png * Delete contentful_logo_with_tagline.png * logos * Added react and contentful logos * Update index.md * Delete React-logo.png * Delete contentful-logo.png * logos smaller * updated intro * Update index.md * [www] Add gatsby-plugin-sentry to list of community plugins (gatsbyjs#3788) * [www] Add gatsby-plugin-meta-redirect to list of community plugins (gatsbyjs#3798) * Form currently refreshes the page on pressing enter (gatsbyjs#3779) * Added some notes on how the contentful source plugin interacts with contentful's content models. (gatsbyjs#3794) * More hot reloading fixes (gatsbyjs#3769) * use createPage singleton in dev-404-page closes gatsbyjs#3551 * write to a temp file and rename decrease the chance of reading from an incomplete file cc gatsbyjs#3094 gatsbyjs#3201 * change dev-404-page to implement createPagesStatefully * update the jest snapshot * Validate starterPath isn't a dot fixes gatsbyjs#3789 (gatsbyjs#3810) * [gatsby] Pass location state to history (gatsbyjs#3802) * Pass full location object to history * Update navigateTo param to be more precise * Pass location to navigateTo in gatsby-link * Update navigateTo types * Fix issue that Gatsby can't sometimes find layout and page files on Windows (gatsbyjs#3796) * Fix issue with missing layouts on Windows * Fix issue with missing pages on Windows * Publish - [email protected] - [email protected] - [email protected] - [email protected] * Add iContract blog to readme (gatsbyjs#3805) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` (gatsbyjs#3801) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` The less plugin did its job, but when I was going to use it with a library I experienced that it was lacking the ability to modify less-variables. This made it hard to customize less libraries. By letting the user provide a `options` in `gatsby-config.js`, the plugin can overwrite variables defined in the less stylesheet and hence makes it a breeze to customize libraries. The user has two options to include vars: either a object defined directly in the `gatsby-config.js` or define a file which exports an object that will be used as the options. * Update README.md * format * Publish - [email protected] - [email protected] - [email protected] * Fix a typo in the gatsby-plugin-less README (gatsbyjs#3815) * Call done() from dev-404-page during production builds so build doesn't stall (gatsbyjs#3827) * Publish - [email protected] - [email protected] * Update README.md (gatsbyjs#3828) * Added logos (gatsbyjs#3781) * Added logos Not sure how to adjust the sizes here. I made them smaller on my computer but not sure if it worked * Reduce React and Contentful logo width to 350px * Log error in createPath (gatsbyjs#3814) Fix conditional to show error when path or component are missing in the createPath function * add warning about query that is not getting executed if it's exported from file that is page/template or layout (gatsbyjs#3786) * Update README.md (gatsbyjs#3821) add module.exports to How to use * Update README.md * Added Hampton starter (gatsbyjs#3826) * [www] add search input to home page (gatsbyjs#3662) * Experiment adding search input to home page * Prettier * Comment unused imports * Display social icons when viewport is wide enough * Use alternate colours at Hd breakpoint on home page * Add name of file above code snippet (gatsbyjs#3835) * [www] Fix typo in styleshout link (gatsbyjs#3839) * Add "Dona Rita" website to Showcase (incl. source) (gatsbyjs#3838) * check markdown images, ensure parent is File before referencing dir (gatsbyjs#3831) * check markdown images, ensure parent is File before referencing dir * add check for parent * [www] Fix typo in docs/building-apps-with-gatsby.md (gatsbyjs#3863) * Bump scroll-behavior dependency to fix ios swipe jank (gatsbyjs#3866) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Fix positioning of search results at mobile breakpoint on homepage (gatsbyjs#3867) * [www] Add tutorial to awesome list (gatsbyjs#3855) This is the first part of a german tutorial series about Gatsby. This part is about the basic creation of a blog. In the next parts I'll cover more advanced features :) * [www] Update Netlify URL in Starter List (gatsbyjs#3847) * Add gatsby-wordpress-starter (gatsbyjs#3848) * exclude offline plugin app shell from sitemap (gatsbyjs#3844) * [gatsby-source-contentful] Add support to prefer WebP images (gatsbyjs#3832) * Extend contentful resolutions and sizes to include webp src and srcSet * Add new contentful fragments * Add fragments to gatsby-image README * Add example for using webp to use-contentful site * Display image examples in a grid * Update docs for adding custom JavaScript to home.js (gatsbyjs#3869) * Blog post headless CMS (gatsbyjs#3846) * Blog post headless CMS A couple things I'm not sure about: - Running sites offline paragraph. Check for accuracy pls! - Better quote from Deane that anyone has in mind? - Can cut down assessment of headless CMSs to omit obscure complaints... * Edits to wording and sprinkling in GatsbyJS Please check paragraph about running sites offline in India! I feel like there's potential there but maybe I'm off base * Update index.md * don't try to extract queries from directories with names ending in .js(x) or .ts (gatsbyjs#3861) * Format * [gatsby-source-filesystem] don't try to process same remote file multiple times, cache promises and return them on subsequent calls (gatsbyjs#3859) * Experimenting (gatsbyjs#3843) * Update README.md (gatsbyjs#3822) add module.exports to How to use * Format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Use HTTPS over git:// when cloning starters (gatsbyjs#3820) `git://` (which is what `hostInfo.git(...)` gets you) uses unencrypted transport isn't recommended as a way to clone GitHub repositories (https://help.github.com/articles/which-remote-url-should-i-use/). This change uses HTTPS instead. * Add gatsby-transformer-screenshot (gatsbyjs#3526) * Add gatsby-plugin-screenshot * Rename to gatsby-transformer-screenshot * Rename * Fix prepublish error * Expand on documentation * Run format-packages * Use API Gateway * Use official deployed Lambda * Update README.md * Format * Publish - [email protected] - [email protected] - [email protected] * [gatsby-plugin-feed] Fix missing colon in Readme (gatsbyjs#3872) * Revert "Use HTTPS over git:// when cloning starters (gatsbyjs#3820)" (gatsbyjs#3876) This reverts commit 8261ac3. * Publish - [email protected] - [email protected] - [email protected] * use simple https to clone starters (gatsbyjs#3875) * Publish - [email protected] - [email protected] * [www] Add gatsby-starter-simple-landing (gatsbyjs#3877) * bigger photo * Update index.md * add www.aslezak.com to showcase (gatsbyjs#3878) * Added new blog, new author and new avatar (gatsbyjs#3879) * Added new blog, new author and new avatar * Fix links * Spelling issue corrected, wp file extension changed and quotes corrected * format blog post * Update index.md (gatsbyjs#3883) * Add community source plugin to docs (gatsbyjs#3884) * [www] Fix small typo (gatsbyjs#3891) * Document all options for gatsby-remark-images fixes gatsbyjs#3882 (gatsbyjs#3894) * Document all options for gatsby-remark-images fixes gatsbyjs#3882 * remove * Edits to wording * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ (gatsbyjs#3887) * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ Ref. gatsbyjs#3886 * Add headline for `PostLink` component * Add possessive adjective * Make code blocks jsx * Add anchors to h1's in docs (gatsbyjs#3892) * Add anchors to h1's in docs * Manually add some anchors * exclude Netlify CMS styles in build-css phase (gatsbyjs#3895) * Fix markdown table syntax in README (gatsbyjs#3897) * Publish - [email protected] - [email protected] - [email protected] * Fix typo (gatsbyjs#3899) * update prismjs-language-dependencies.js (gatsbyjs#3898) * Publish - [email protected] - [email protected] * Update snapshots and packages and format w/ new Prettier (gatsbyjs#3902) * Update snapshots and packages and format w/ new Prettier * Update snapshot in embed package * [gatsby-transformer-remark] Add `pathPrefix` to relative links (gatsbyjs#3823) * [gatsby-transformer-remark] Add `pathPrefix` to relative links Ensure markdown relative links include `pathPrefix`. Fixes gatsbyjs#3316 * [gatsby-transformer-remark] add minor comment to `withPathPrefix` * [gatsby-transformer-remark] add `pathPrefix` to `cacheKey` functions * [gatsby-transformer-remark] remove `node.url.startsWith(pathPrefix)` condition for `withPathPrefix` logic * Use "npm-run-all" to run scripts (gatsbyjs#3797) * Use "npm-run-all" to run scripts [npm-run-all](https://github.com/mysticatea/npm-run-all) is a cross-browser approach to running npm tasks in series (`-s`) or parallel (`-p`). Rather than using a platform specific method to run scripts (e.g. `&&`), npm-run-all will work on all platforms and supports using Yarn if running with Yarn. I made a guess as to whether certain scripts should be run in series or parallel but feel free to change if my choices aren't optimal. * Add yarn.lock and fix some scripts. * Move npm-run-all to dev dep. * Fix bootstrap script. * [www] Starters: Fix case according to vendor name definition (gatsbyjs#3903) * http://getbootstrap.com/ * http://postcss.org/ * https://sass-lang.com/ * https://bootswatch.com/ * Publish - [email protected] - [email protected] - [email protected] - [email protected] * add info about org-mode transformer plugin (gatsbyjs#3907) I created this transformer plugin similar to the offical remark one, that parses org-mode files. * [www] add gatsby-orga starter (gatsbyjs#3908) * update odayaka.net to showcase (gatsbyjs#3909) update odayaka.net to showcase * [www] Add ventura-digital.de to Showcase (gatsbyjs#3916) * Minor edits for absolute beginners After doing this tutorial as a complete beginner myself, I thought a couple of lines could be made even more newby-friendly. * Update tutorial.js (gatsbyjs#3927) * ✨ Support filtering on linked nodes (gatsbyjs#3691) * ✨ Support filtering on linked nodes The filtering is done by extracting all the related nodes using `extractFieldExample`. The example values are then cached to save some time. (As of this patch, caching is not tested automatically) Further linking are disabled to avoid cyclic dependencies (input fields only). TODO: Filtering on nodes linked by mappings and File Note: If linking is done via array of IDs, only the structure of the first item is extracted. I'll be happy to add union support if someone can show me how to `$in` filter on an array of object. Related gatsbyjs#3613 gatsbyjs#3190 * ✅ Test filtering on linked nodes * Publish - [email protected] * Set default NODE_ENV for `gatsby develop` (gatsbyjs#3928) * Fix broken links (gatsbyjs#3930) * Blog Post - Jam Out Your Blog (gatsbyjs#3911) * Blog Post - Jam Out Your Blog Vlad Pasculescu’s blog post on using Gatsby with Netify and Prose.io Signed-off-by: vladpasculescu <[email protected]> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - [email protected] - [email protected] * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes (gatsbyjs#3522) * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes Fixes: gatsbyjs#3521 * refactor(dev-404-page): use RegExp.test() as we don't need to return anything * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes updating other occurrence of 404 page check as well * Automatic file validation for components in src/pages (gatsbyjs#3881) * yarn.lock * add page validation and fix breaking createPage action tests * Improve error messages for invalid pages * Field inferring changes and cleanup (gatsbyjs#3688) * remove not needed edge case for infering array of objects to improve code readability * don't lose field args and resolve function when infering array (fixes date format options not available in arrays of dates) * move infering date field to seperate file to improve code readability * don't recreate date field definition for every date field - we can reuse same object * create dedicated Date graphql scalar (based on string scalar) for date fields * pass fieldName to resolver when filtering on types with custom resolvers (date type fields now rely on fieldname info being passed) * use already constructed nextselector instead of rebuilding it again * move infering file field to separate file to improve code readability * create file type field object just once and reuse it * move trying to infer Files from string paths to inferGraphQLType function where rest of value based inferring is done * add tests for inferring File from string paths * add tests for inferring date type from string, array of strings and filtering date fields, move date related test to seperate date test suite * Publish - [email protected] * Return a never to be resolved promise to prevent development server from exiting early fixes gatsbyjs#3932 (gatsbyjs#3933) * Publish - [email protected] - [email protected] * format * Add Cardiogram to README (gatsbyjs#3934) * Fix code highlight in tutorial (gatsbyjs#3935) * small wording change * [api-ssr-docs] Import `Helmet` not `helmet` (gatsbyjs#3940) * [www] Tutorial: Small wording changes for clarification (gatsbyjs#3926) gatsby-config.js needs to be created (before edited). Also, since the user will be changing windows to stop the process it might be useful to remind them where they were before. * [docs] Fix small typo (gatsbyjs#3946) * test "exports.default" when validating page component (gatsbyjs#3941) * Publish - [email protected] * update environment variables docs to explain how to implement dotenv (gatsbyjs#3944) * [www] Add dedicated „How to File an Issue“ page (gatsbyjs#3945) * move „Filing an Issue“ and „Special Note on Issues“ from the „How to Contribute“ to the new „How to File an Issue“ page * add an intro paragraph to the new page linking to the GitHub Gatsby issue tracker * add a paragraph to the new page informing about personal support requests, pointing to Stack Overflow, Reactiflux Discord * add link to the new page to * the docs sidebar’s „Contributing“ section * the GitHub issue template * the „Community“ page * the list of ways to contribute on the „How to Contribute“ page * link „Triaging GitHub issues“ on the „How to Contribute“ page * Don't check if React is imported as can import component from other page and never write JSX (gatsbyjs#3949) /cc @bodia-uz * Publish - [email protected] * Add LaserTime Clinic website to Readme (gatsbyjs#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (gatsbyjs#3952) * Publish - [email protected] * type inferring - handle array of Date objects (gatsbyjs#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - [email protected] * Document how to create custom fragments (gatsbyjs#3914) * Document how to create custom fragments * Fix ordering * Add example component exporting a fragment * Tweak language * Update index.md (gatsbyjs#3957) * update showcase with Gatsby Manor (gatsbyjs#3959) Gatsby Manor makes themes for GatsbyJS. * Adds new starter to docs :) (gatsbyjs#3971) * Fix error (gatsbyjs#3985) Talked to Ross Whitehouse, the author, via Medium private message to confirm the errors. Gotten permission to submit PR for the edit. * Add note about plugin options (gatsbyjs#3987) * Add container as a styled div to styled-components doc (gatsbyjs#3988) * Add Dockerfile to start GraphiQL using www's data (gatsbyjs#3992) * fix: prevent invalid graphql field names from being created (gatsbyjs#3994) * fix: prevent invalid graphql field names from being created Note: This will currently transform (for example) `/*` into `_` so I'm not quite sure what the best course of action is to replace that Fixes gatsbyjs#3487; Fixes gatsbyjs#2925 * chore: revert yarn lock change * test: simplify tests * fix: dasherize after leading underscore * feat(gatsby-plugin-google-analytics): add head option (gatsbyjs#3995) Add head option to configure whether scrip tag should be put in the body (by default, same as previously) or inside of the head. closes gatsbyjs#2894 * Add browserAPIs and ssrAPIs to loaded plugin info (gatsbyjs#3989) * Add browserAPIs and ssrAPIs to loaded plugin info * Output correct error message for each bad export * Use lodash for Node 6 compatibility * Publish - [email protected] - [email protected] * add package json metadata for better display on npmjs.org (gatsbyjs#3981) * chore: add package json metadata (git url, issues, etc.) * chore: update plop template * chore: move bin/files up in package.json * chore: fix unescaped email(s) * Run 'fixpack' on all package.jsons * Validate when creating a page that the page component exists (gatsbyjs#3997) * Validate when creating a page that the page component exists * Don't check for component paths during testing as it breaks tests * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-transformer-react-docgen] Add note on PropTypes (gatsbyjs#4008) * Update adding-tags-and-categories-to-blog-posts.md (gatsbyjs#3999) Changed per a conversation with Kyle about a better way to do this. Relates to gatsbyjs#3976 * [gatsby-remark-katex] Upgrade remark-math to latest (gatsbyjs#4005) * update remark-math to latest version to fix an issue where equations surrounded by `$$` with new lines are not displayed in KaTeX' `displayMode` * update broken spec * add spec for display math node * [using-remark] fix "Math Equations in Display Mode" example * Add note about using Custom Domain with Github Pages (gatsbyjs#4006) * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * [docs] Add Gatsby Manor blog post (gatsbyjs#3968) Show the community Gatsby Manor. * don't use internal-only path when requiring promise polyfill (gatsbyjs#4012) see: zloirock/core-js#138 (comment) * Fix tracking parent nodes when loading redux state from cache (gatsbyjs#4013) fixes gatsbyjs#2929 * Publish - [email protected] - [email protected] - [email protected] * Add info about gatsby-plugin-sharp (gatsbyjs#4019) * Add info about gatsby-plugin-sharp * Update README.md * update contributing documentation to mention that npm run watch can be resource intensive, and suggest watching select packages at a time (gatsbyjs#4020) * [gatsby-image] Allow specifying HTML tag for gatsby-image wrapping elements (gatsbyjs#4022) * Allow specifying which html tag will be used for gatsby-image wrappers * Update gatsby-image README.md to include new Tag prop * Fix plugin loader checks (gatsbyjs#4023) * Add browser and SSR APIs to the plugin API whitelist * Add registerServiceWorker to the list of allowed browser APIs * Publish - [email protected] - [email protected] * Fix tracking nodes with filtering/running sift (gatsbyjs#4024) * Track Node that contains inline objects/arrays instead of its parent. This doesn't break finding topmost ancestor node as we already trying to get walk along parent hierarchy. Rename tracking functions and jsdocs to provide some basic context for these functions * Fix tracking nodes with filtering/running sift. Before we filter nodes we create copies of nodes with appended fields added by plugins (by setFieldsOnGraphQLNodeType) if they are filtered on. These copies weren't tracked. * fix: add info message if gatsby-config.js could have been typo'd (gatsbyjs#4017) * fix: add info message if gatsby-config.js could have been typo'd * chore: move preferDefault back to where it was * refactor: tweak error logic a bit * chore: tweak versions for yarn.lock compat * refactor: address PR comments * fix: fail with error * format * Fix lint errors * fix: ensure graphql key is a valid graphql key value (gatsbyjs#4000) * fix: ensure graphql key is a valid graphql key value * chore: update comment * Improve the warning for when someone includes a graphql query in a non-page component (gatsbyjs#4026) * Publish - [email protected] * add gatsby-transformer-javascript-frontmatter, closes gatsbyjs#3795 (gatsbyjs#3947) * initial commit * update name in package.json * start converting example site * fix gql error on js articles * rename intial defined `let` * clear out unused deps * begin updating new layout components * fix all HOC * update example readme * Format * Update README.md * Catch require error for hot-reloading gatsby-config.js fixes gatsbyjs#3990 (gatsbyjs#4039) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Don't exit on errors as during development, empty/incomplete page components are common fixes gatsbyjs#4027 (gatsbyjs#4040) * Don't exit on errors as during development, empty/incomplete page components are common fixes gatsbyjs#4027 * Fix other points of death * Ok, do die here * Remove component query from store when a user deletes it fixes gatsbyjs#4032 (gatsbyjs#4041) * Publish - [email protected] * add portfolio site to the readme showcase (gatsbyjs#4043) * Add documentation for using boundActionCreators fixes gatsbyjs#4029 (gatsbyjs#4042) * Add documentation for using boundActionCreators * Update bound-action-creators.js * Fix * node tracking - add tests (gatsbyjs#4045) * move node tracking code to separate dedicated file * Add jsdoc for findRootNode * add tests for node tracking * Update README.md * Add links to the end of the tutorial (gatsbyjs#4051) * [www] Fix tutorial sidebar links active state, update deps (gatsbyjs#4059) * Bump deps, add react-helmet for gatsby-plugin-react-helmet v2 * Fix warning „Warning: Received `false` for non-boolean attribute `className`. If this is expected, cast the value to a string.“ * Update preload href * Rewire sidebar section and link styles, fix gatsbyjs#4036 * Use babylon to parse out exports from plugin files (gatsbyjs#4057) * Fixes * Fix package.json * Fix package.json * Ignore tests * Fix lint * Comment out less tests until theme functionality can be ported to v2

@bodia-uz

* Revert "Update gatsby-browser.js (gatsbyjs#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (gatsbyjs#3717) * Publish - [email protected] * Add missing (official) plugins & little fixes (gatsbyjs#3718) * Add missing (official) plugins & little fixes As talked about in: gatsbyjs#3708 Fingers crossed that I didn't mess up the alphabetical order :P (I actually changed the order a little bit) * Add gatsby-source-graphcms * fix(transformer-remark): resolve htmlAst correctly (gatsbyjs#3719) closes gatsbyjs#3711 * Added my new websites to showcase (gatsbyjs#3729) * Adjust default link header value in netlify plugin readme (gatsbyjs#3723) * Change "primatives" to "primitives" in GraphQL docs (gatsbyjs#3716) * [gatsby-transformer-remark] Reparse `raw` nodes in `htmlAst` (gatsbyjs#3731) Preprocessing via `gatsby-remark-*` transformations introduces `raw` nodes into the AST. Adding this step fully enables the client to render the AST as React components, finishing the work started in gatsbyjs#3596. * Publish - [email protected] - [email protected] - [email protected] - [email protected] * fix(gatsby-link): correct dependency declaration (gatsbyjs#3707) * fix(gatsby-link): correct dependency declaration The code depends on `react-router-dom`, and therefore it should be declared as a direct dependency, not a dev one. Also, it needs `@types/react-router-dom` for index.d.ts. * chore(gatsby-link): declare gatsby v1 as a peer dependency * Publish - [email protected] - [email protected] * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (gatsbyjs#3735) * Publish - [email protected] - [email protected] * Update CONTRIBUTING.md (gatsbyjs#3737) incorrect usage of "it's" * Add freeCodeCamp source (gatsbyjs#3739) * Add Hack Club to projects list (gatsbyjs#3748) * Link title not particularly accurate * Fix link syntax (gatsbyjs#3749) * add basic documentation about publicURL field on File node (gatsbyjs#3752) * add basic documentation about copying files from File nodes to build directory * A few copy edits * Format * Format * [www] Fix link to "Adding Markdown Pages" in List docs (gatsbyjs#3747) * [www] Add "gatsby-plugin-fela" to list of community plugins * Semi-Colons (gatsbyjs#3764) * Remove mention of not-written part 5 of the tutorial * [www] Add ERC dEX website to showcase (gatsbyjs#3766) * make ComponentRenderer shouldUpdateComponent return true when props c… (gatsbyjs#3516) * make ComponentRenderer shouldUpdateComponent return true when props change * use shallow compare * remove console log * semi-colons (gatsbyjs#3765) * [gatsby] Report an error when layout file is missing (gatsbyjs#3762) * [gatsby] Report an error when layout file is missing * Update pages-writer.js * format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath (gatsbyjs#3211) * [gatsby-plugin-netlify] create rewrite rules for pages that use matchPath * Update README.md * Add a no-color option to disable the colors (gatsbyjs#3755) * disable boolean-negation in yargs * add no-color option * [www] Add gatsby-source-unsplash to list of community plugins (gatsbyjs#3768) * format * Publish - [email protected] - [email protected] - [email protected] * Add setTimeout before calling onRouteUpdate to ensure React has written to DOM before plugins run code (gatsbyjs#3772) * Improve errors for invalid data passed to createPage fixes gatsbyjs#3771 (gatsbyjs#3773) * Fix not scrolling to top on PUSH fixes gatsbyjs#3770 gatsbyjs#3249 (gatsbyjs#3775) * [examples/using-remark]: Custom React components in Markdown files (gatsbyjs#3732) * Publish - [email protected] - [email protected] - [email protected] - [email protected] * [www] Prevent search shortcut from breaking other input elements (gatsbyjs#3777) * Edits from Ben's feedback * Logos * Delete React_logo_wordmark.png * Delete contentful_logo_with_tagline.png * logos * Added react and contentful logos * Update index.md * Delete React-logo.png * Delete contentful-logo.png * logos smaller * updated intro * Update index.md * [www] Add gatsby-plugin-sentry to list of community plugins (gatsbyjs#3788) * [www] Add gatsby-plugin-meta-redirect to list of community plugins (gatsbyjs#3798) * Form currently refreshes the page on pressing enter (gatsbyjs#3779) * Added some notes on how the contentful source plugin interacts with contentful's content models. (gatsbyjs#3794) * More hot reloading fixes (gatsbyjs#3769) * use createPage singleton in dev-404-page closes gatsbyjs#3551 * write to a temp file and rename decrease the chance of reading from an incomplete file cc gatsbyjs#3094 gatsbyjs#3201 * change dev-404-page to implement createPagesStatefully * update the jest snapshot * Validate starterPath isn't a dot fixes gatsbyjs#3789 (gatsbyjs#3810) * [gatsby] Pass location state to history (gatsbyjs#3802) * Pass full location object to history * Update navigateTo param to be more precise * Pass location to navigateTo in gatsby-link * Update navigateTo types * Fix issue that Gatsby can't sometimes find layout and page files on Windows (gatsbyjs#3796) * Fix issue with missing layouts on Windows * Fix issue with missing pages on Windows * Publish - [email protected] - [email protected] - [email protected] - [email protected] * Add iContract blog to readme (gatsbyjs#3805) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` (gatsbyjs#3801) * [gatsby-plugin-less] Extend less-plugin with support for `modifyVars` The less plugin did its job, but when I was going to use it with a library I experienced that it was lacking the ability to modify less-variables. This made it hard to customize less libraries. By letting the user provide a `options` in `gatsby-config.js`, the plugin can overwrite variables defined in the less stylesheet and hence makes it a breeze to customize libraries. The user has two options to include vars: either a object defined directly in the `gatsby-config.js` or define a file which exports an object that will be used as the options. * Update README.md * format * Publish - [email protected] - [email protected] - [email protected] * Fix a typo in the gatsby-plugin-less README (gatsbyjs#3815) * Call done() from dev-404-page during production builds so build doesn't stall (gatsbyjs#3827) * Publish - [email protected] - [email protected] * Update README.md (gatsbyjs#3828) * Added logos (gatsbyjs#3781) * Added logos Not sure how to adjust the sizes here. I made them smaller on my computer but not sure if it worked * Reduce React and Contentful logo width to 350px * Log error in createPath (gatsbyjs#3814) Fix conditional to show error when path or component are missing in the createPath function * add warning about query that is not getting executed if it's exported from file that is page/template or layout (gatsbyjs#3786) * Update README.md (gatsbyjs#3821) add module.exports to How to use * Update README.md * Added Hampton starter (gatsbyjs#3826) * [www] add search input to home page (gatsbyjs#3662) * Experiment adding search input to home page * Prettier * Comment unused imports * Display social icons when viewport is wide enough * Use alternate colours at Hd breakpoint on home page * Add name of file above code snippet (gatsbyjs#3835) * [www] Fix typo in styleshout link (gatsbyjs#3839) * Add "Dona Rita" website to Showcase (incl. source) (gatsbyjs#3838) * check markdown images, ensure parent is File before referencing dir (gatsbyjs#3831) * check markdown images, ensure parent is File before referencing dir * add check for parent * [www] Fix typo in docs/building-apps-with-gatsby.md (gatsbyjs#3863) * Bump scroll-behavior dependency to fix ios swipe jank (gatsbyjs#3866) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Fix positioning of search results at mobile breakpoint on homepage (gatsbyjs#3867) * [www] Add tutorial to awesome list (gatsbyjs#3855) This is the first part of a german tutorial series about Gatsby. This part is about the basic creation of a blog. In the next parts I'll cover more advanced features :) * [www] Update Netlify URL in Starter List (gatsbyjs#3847) * Add gatsby-wordpress-starter (gatsbyjs#3848) * exclude offline plugin app shell from sitemap (gatsbyjs#3844) * [gatsby-source-contentful] Add support to prefer WebP images (gatsbyjs#3832) * Extend contentful resolutions and sizes to include webp src and srcSet * Add new contentful fragments * Add fragments to gatsby-image README * Add example for using webp to use-contentful site * Display image examples in a grid * Update docs for adding custom JavaScript to home.js (gatsbyjs#3869) * Blog post headless CMS (gatsbyjs#3846) * Blog post headless CMS A couple things I'm not sure about: - Running sites offline paragraph. Check for accuracy pls! - Better quote from Deane that anyone has in mind? - Can cut down assessment of headless CMSs to omit obscure complaints... * Edits to wording and sprinkling in GatsbyJS Please check paragraph about running sites offline in India! I feel like there's potential there but maybe I'm off base * Update index.md * don't try to extract queries from directories with names ending in .js(x) or .ts (gatsbyjs#3861) * Format * [gatsby-source-filesystem] don't try to process same remote file multiple times, cache promises and return them on subsequent calls (gatsbyjs#3859) * Experimenting (gatsbyjs#3843) * Update README.md (gatsbyjs#3822) add module.exports to How to use * Format * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Use HTTPS over git:// when cloning starters (gatsbyjs#3820) `git://` (which is what `hostInfo.git(...)` gets you) uses unencrypted transport isn't recommended as a way to clone GitHub repositories (https://help.github.com/articles/which-remote-url-should-i-use/). This change uses HTTPS instead. * Add gatsby-transformer-screenshot (gatsbyjs#3526) * Add gatsby-plugin-screenshot * Rename to gatsby-transformer-screenshot * Rename * Fix prepublish error * Expand on documentation * Run format-packages * Use API Gateway * Use official deployed Lambda * Update README.md * Format * Publish - [email protected] - [email protected] - [email protected] * [gatsby-plugin-feed] Fix missing colon in Readme (gatsbyjs#3872) * Revert "Use HTTPS over git:// when cloning starters (gatsbyjs#3820)" (gatsbyjs#3876) This reverts commit 8261ac3. * Publish - [email protected] - [email protected] - [email protected] * use simple https to clone starters (gatsbyjs#3875) * Publish - [email protected] - [email protected] * [www] Add gatsby-starter-simple-landing (gatsbyjs#3877) * bigger photo * Update index.md * add www.aslezak.com to showcase (gatsbyjs#3878) * Added new blog, new author and new avatar (gatsbyjs#3879) * Added new blog, new author and new avatar * Fix links * Spelling issue corrected, wp file extension changed and quotes corrected * format blog post * Update index.md (gatsbyjs#3883) * Add community source plugin to docs (gatsbyjs#3884) * [www] Fix small typo (gatsbyjs#3891) * Document all options for gatsby-remark-images fixes gatsbyjs#3882 (gatsbyjs#3894) * Document all options for gatsby-remark-images fixes gatsbyjs#3882 * remove * Edits to wording * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ (gatsbyjs#3887) * [www] Add `PostLink` component example to docs/adding-a-list-of-markdown-blog-posts/ Ref. gatsbyjs#3886 * Add headline for `PostLink` component * Add possessive adjective * Make code blocks jsx * Add anchors to h1's in docs (gatsbyjs#3892) * Add anchors to h1's in docs * Manually add some anchors * exclude Netlify CMS styles in build-css phase (gatsbyjs#3895) * Fix markdown table syntax in README (gatsbyjs#3897) * Publish - [email protected] - [email protected] - [email protected] * Fix typo (gatsbyjs#3899) * update prismjs-language-dependencies.js (gatsbyjs#3898) * Publish - [email protected] - [email protected] * Update snapshots and packages and format w/ new Prettier (gatsbyjs#3902) * Update snapshots and packages and format w/ new Prettier * Update snapshot in embed package * [gatsby-transformer-remark] Add `pathPrefix` to relative links (gatsbyjs#3823) * [gatsby-transformer-remark] Add `pathPrefix` to relative links Ensure markdown relative links include `pathPrefix`. Fixes gatsbyjs#3316 * [gatsby-transformer-remark] add minor comment to `withPathPrefix` * [gatsby-transformer-remark] add `pathPrefix` to `cacheKey` functions * [gatsby-transformer-remark] remove `node.url.startsWith(pathPrefix)` condition for `withPathPrefix` logic * Use "npm-run-all" to run scripts (gatsbyjs#3797) * Use "npm-run-all" to run scripts [npm-run-all](https://github.com/mysticatea/npm-run-all) is a cross-browser approach to running npm tasks in series (`-s`) or parallel (`-p`). Rather than using a platform specific method to run scripts (e.g. `&&`), npm-run-all will work on all platforms and supports using Yarn if running with Yarn. I made a guess as to whether certain scripts should be run in series or parallel but feel free to change if my choices aren't optimal. * Add yarn.lock and fix some scripts. * Move npm-run-all to dev dep. * Fix bootstrap script. * [www] Starters: Fix case according to vendor name definition (gatsbyjs#3903) * http://getbootstrap.com/ * http://postcss.org/ * https://sass-lang.com/ * https://bootswatch.com/ * Publish - [email protected] - [email protected] - [email protected] - [email protected] * add info about org-mode transformer plugin (gatsbyjs#3907) I created this transformer plugin similar to the offical remark one, that parses org-mode files. * [www] add gatsby-orga starter (gatsbyjs#3908) * update odayaka.net to showcase (gatsbyjs#3909) update odayaka.net to showcase * [www] Add ventura-digital.de to Showcase (gatsbyjs#3916) * Minor edits for absolute beginners After doing this tutorial as a complete beginner myself, I thought a couple of lines could be made even more newby-friendly. * Update tutorial.js (gatsbyjs#3927) * ✨ Support filtering on linked nodes (gatsbyjs#3691) * ✨ Support filtering on linked nodes The filtering is done by extracting all the related nodes using `extractFieldExample`. The example values are then cached to save some time. (As of this patch, caching is not tested automatically) Further linking are disabled to avoid cyclic dependencies (input fields only). TODO: Filtering on nodes linked by mappings and File Note: If linking is done via array of IDs, only the structure of the first item is extracted. I'll be happy to add union support if someone can show me how to `$in` filter on an array of object. Related gatsbyjs#3613 gatsbyjs#3190 * ✅ Test filtering on linked nodes * Publish - [email protected] * Set default NODE_ENV for `gatsby develop` (gatsbyjs#3928) * Fix broken links (gatsbyjs#3930) * Blog Post - Jam Out Your Blog (gatsbyjs#3911) * Blog Post - Jam Out Your Blog Vlad Pasculescu’s blog post on using Gatsby with Netify and Prose.io Signed-off-by: vladpasculescu <[email protected]> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - [email protected] - [email protected] * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes (gatsbyjs#3522) * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes Fixes: gatsbyjs#3521 * refactor(dev-404-page): use RegExp.test() as we don't need to return anything * fix(dev-404-page): route to 404 fails when using plugin-remove-trailing-slashes updating other occurrence of 404 page check as well * Automatic file validation for components in src/pages (gatsbyjs#3881) * yarn.lock * add page validation and fix breaking createPage action tests * Improve error messages for invalid pages * Field inferring changes and cleanup (gatsbyjs#3688) * remove not needed edge case for infering array of objects to improve code readability * don't lose field args and resolve function when infering array (fixes date format options not available in arrays of dates) * move infering date field to seperate file to improve code readability * don't recreate date field definition for every date field - we can reuse same object * create dedicated Date graphql scalar (based on string scalar) for date fields * pass fieldName to resolver when filtering on types with custom resolvers (date type fields now rely on fieldname info being passed) * use already constructed nextselector instead of rebuilding it again * move infering file field to separate file to improve code readability * create file type field object just once and reuse it * move trying to infer Files from string paths to inferGraphQLType function where rest of value based inferring is done * add tests for inferring File from string paths * add tests for inferring date type from string, array of strings and filtering date fields, move date related test to seperate date test suite * Publish - [email protected] * Return a never to be resolved promise to prevent development server from exiting early fixes gatsbyjs#3932 (gatsbyjs#3933) * Publish - [email protected] - [email protected] * format * Add Cardiogram to README (gatsbyjs#3934) * Fix code highlight in tutorial (gatsbyjs#3935) * small wording change * [api-ssr-docs] Import `Helmet` not `helmet` (gatsbyjs#3940) * [www] Tutorial: Small wording changes for clarification (gatsbyjs#3926) gatsby-config.js needs to be created (before edited). Also, since the user will be changing windows to stop the process it might be useful to remind them where they were before. * [docs] Fix small typo (gatsbyjs#3946) * test "exports.default" when validating page component (gatsbyjs#3941) * Publish - [email protected] * update environment variables docs to explain how to implement dotenv (gatsbyjs#3944) * [www] Add dedicated „How to File an Issue“ page (gatsbyjs#3945) * move „Filing an Issue“ and „Special Note on Issues“ from the „How to Contribute“ to the new „How to File an Issue“ page * add an intro paragraph to the new page linking to the GitHub Gatsby issue tracker * add a paragraph to the new page informing about personal support requests, pointing to Stack Overflow, Reactiflux Discord * add link to the new page to * the docs sidebar’s „Contributing“ section * the GitHub issue template * the „Community“ page * the list of ways to contribute on the „How to Contribute“ page * link „Triaging GitHub issues“ on the „How to Contribute“ page * Don't check if React is imported as can import component from other page and never write JSX (gatsbyjs#3949) /cc @bodia-uz * Publish - [email protected] * Add LaserTime Clinic website to Readme (gatsbyjs#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (gatsbyjs#3952) * Publish - [email protected] * type inferring - handle array of Date objects (gatsbyjs#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - [email protected] * Document how to create custom fragments (gatsbyjs#3914) * Document how to create custom fragments * Fix ordering * Add example component exporting a fragment * Tweak language * Update index.md (gatsbyjs#3957) * update showcase with Gatsby Manor (gatsbyjs#3959) Gatsby Manor makes themes for GatsbyJS. * Adds new starter to docs :) (gatsbyjs#3971) * Fix error (gatsbyjs#3985) Talked to Ross Whitehouse, the author, via Medium private message to confirm the errors. Gotten permission to submit PR for the edit. * Add note about plugin options (gatsbyjs#3987) * Add container as a styled div to styled-components doc (gatsbyjs#3988) * Add Dockerfile to start GraphiQL using www's data (gatsbyjs#3992) * fix: prevent invalid graphql field names from being created (gatsbyjs#3994) * fix: prevent invalid graphql field names from being created Note: This will currently transform (for example) `/*` into `_` so I'm not quite sure what the best course of action is to replace that Fixes gatsbyjs#3487; Fixes gatsbyjs#2925 * chore: revert yarn lock change * test: simplify tests * fix: dasherize after leading underscore * feat(gatsby-plugin-google-analytics): add head option (gatsbyjs#3995) Add head option to configure whether scrip tag should be put in the body (by default, same as previously) or inside of the head. closes gatsbyjs#2894 * Add browserAPIs and ssrAPIs to loaded plugin info (gatsbyjs#3989) * Add browserAPIs and ssrAPIs to loaded plugin info * Output correct error message for each bad export * Use lodash for Node 6 compatibility * Publish - [email protected] - [email protected] * add package json metadata for better display on npmjs.org (gatsbyjs#3981) * chore: add package json metadata (git url, issues, etc.) * chore: update plop template * chore: move bin/files up in package.json * chore: fix unescaped email(s) * Run 'fixpack' on all package.jsons * Validate when creating a page that the page component exists (gatsbyjs#3997) * Validate when creating a page that the page component exists * Don't check for component paths during testing as it breaks tests * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [gatsby-transformer-react-docgen] Add note on PropTypes (gatsbyjs#4008) * Update adding-tags-and-categories-to-blog-posts.md (gatsbyjs#3999) Changed per a conversation with Kyle about a better way to do this. Relates to gatsbyjs#3976 * [gatsby-remark-katex] Upgrade remark-math to latest (gatsbyjs#4005) * update remark-math to latest version to fix an issue where equations surrounded by `$$` with new lines are not displayed in KaTeX' `displayMode` * update broken spec * add spec for display math node * [using-remark] fix "Math Equations in Display Mode" example * Add note about using Custom Domain with Github Pages (gatsbyjs#4006) * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * Update how-gatsby-works-with-github-pages.md * [docs] Add Gatsby Manor blog post (gatsbyjs#3968) Show the community Gatsby Manor. * don't use internal-only path when requiring promise polyfill (gatsbyjs#4012) see: zloirock/core-js#138 (comment) * Fix tracking parent nodes when loading redux state from cache (gatsbyjs#4013) fixes gatsbyjs#2929 * Publish - [email protected] - [email protected] - [email protected] * Add info about gatsby-plugin-sharp (gatsbyjs#4019) * Add info about gatsby-plugin-sharp * Update README.md * update contributing documentation to mention that npm run watch can be resource intensive, and suggest watching select packages at a time (gatsbyjs#4020) * [gatsby-image] Allow specifying HTML tag for gatsby-image wrapping elements (gatsbyjs#4022) * Allow specifying which html tag will be used for gatsby-image wrappers * Update gatsby-image README.md to include new Tag prop * Fix plugin loader checks (gatsbyjs#4023) * Add browser and SSR APIs to the plugin API whitelist * Add registerServiceWorker to the list of allowed browser APIs * Publish - [email protected] - [email protected] * Fix tracking nodes with filtering/running sift (gatsbyjs#4024) * Track Node that contains inline objects/arrays instead of its parent. This doesn't break finding topmost ancestor node as we already trying to get walk along parent hierarchy. Rename tracking functions and jsdocs to provide some basic context for these functions * Fix tracking nodes with filtering/running sift. Before we filter nodes we create copies of nodes with appended fields added by plugins (by setFieldsOnGraphQLNodeType) if they are filtered on. These copies weren't tracked. * fix: add info message if gatsby-config.js could have been typo'd (gatsbyjs#4017) * fix: add info message if gatsby-config.js could have been typo'd * chore: move preferDefault back to where it was * refactor: tweak error logic a bit * chore: tweak versions for yarn.lock compat * refactor: address PR comments * fix: fail with error * format * Fix lint errors * fix: ensure graphql key is a valid graphql key value (gatsbyjs#4000) * fix: ensure graphql key is a valid graphql key value * chore: update comment * Improve the warning for when someone includes a graphql query in a non-page component (gatsbyjs#4026) * Publish - [email protected] * add gatsby-transformer-javascript-frontmatter, closes gatsbyjs#3795 (gatsbyjs#3947) * initial commit * update name in package.json * start converting example site * fix gql error on js articles * rename intial defined `let` * clear out unused deps * begin updating new layout components * fix all HOC * update example readme * Format * Update README.md * Catch require error for hot-reloading gatsby-config.js fixes gatsbyjs#3990 (gatsbyjs#4039) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * Don't exit on errors as during development, empty/incomplete page components are common fixes gatsbyjs#4027 (gatsbyjs#4040) * Don't exit on errors as during development, empty/incomplete page components are common fixes gatsbyjs#4027 * Fix other points of death * Ok, do die here * Remove component query from store when a user deletes it fixes gatsbyjs#4032 (gatsbyjs#4041) * Publish - [email protected] * add portfolio site to the readme showcase (gatsbyjs#4043) * Add documentation for using boundActionCreators fixes gatsbyjs#4029 (gatsbyjs#4042) * Add documentation for using boundActionCreators * Update bound-action-creators.js * Fix * node tracking - add tests (gatsbyjs#4045) * move node tracking code to separate dedicated file * Add jsdoc for findRootNode * add tests for node tracking * Update README.md * Add links to the end of the tutorial (gatsbyjs#4051) * [www] Fix tutorial sidebar links active state, update deps (gatsbyjs#4059) * Bump deps, add react-helmet for gatsby-plugin-react-helmet v2 * Fix warning „Warning: Received `false` for non-boolean attribute `className`. If this is expected, cast the value to a string.“ * Update preload href * Rewire sidebar section and link styles, fix gatsbyjs#4036 * Use babylon to parse out exports from plugin files (gatsbyjs#4057) * Minor typo fix (gatsbyjs#4063) * sort type names when creating union type name to keep union type names more consistent (gatsbyjs#4074) previously this name would change when order of source data change * Publish - [email protected] - [email protected] * Update minimum Node.js versions (gatsbyjs#4075) * support tiff images and don't get stuck indefinitely when used, add basic error checking (gatsbyjs#4076) * Remove .travis.yml file from www directory as it's never been used (gatsbyjs#4082) * [www] Tutorial: Highlight closing tag (gatsbyjs#3925) * Highlight closing tag There are two additions to the code, however only the opening div is highlighted and not its closing tag. * Made changes suggested by Yisela @yisela, I changed this! It took a while for me to figure out, which means that most beginners would also have trouble figuring it out, haha. Thanks for noticing and helping Gatsby improve!!! * Revert "define webpack loader.exclude with array for extensibility" (gatsbyjs#4046) This reverts commit 50b0a47. * Add documentation for mapping in gatsby-config (gatsbyjs#4054) * Add documentation for mapping * Fix glitch in pasted code * Update gatsby-config.md * format * Update gatsby-config.md * Update gatsby-config.md * Add new Tools-section and mention Gatsby-Docker (gatsbyjs#4085) As suggested here: https://twitter.com/gatsbyjs/status/964531323606986752 * Remove ReasonML site (gatsbyjs#4084) * Added gatsby-source-dribbble plugin (gatsbyjs#4086) Added gatsby-source-dribbble plugin to community plugins * Adds add'l docs to gatsby-source-filesystem (gatsbyjs#4060) * Adds add'l docs to gatsby-source-filesystem * Update README.md * Format * [docs] Add A Bright Future For The Web blog post (gatsbyjs#4073) * Blogpost (gatsbyjs#4083) * Blogpost Hope this is good to go. I feel like it's kind of boring and abstract. Hoped to have more examples or stories or screenshots but don't know enough to add more! * Update index.md Removed some content which felt a bit extraneous + corrected a few descriptions of React * Add portfolio of Preston Richey to README showcase (gatsbyjs#4087) * gatsby.org -> gatsbyjs.org (gatsbyjs#4088) * gatsby.org -> gatsbyjs.org * Update index.md * fix broken `path` dependency (gatsbyjs#4090) Following the guide I had an error with the `path`. It seems that requiring it at the top of the file solves the issue: `const path = require("path");` Is there something else I was missing? Cheers * Remove tiff option from gatsby-plugin-sharp as it's converting all images to tiff (gatsbyjs#4091) * Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * [www] Fix quotes, fixes „Invalid date“ of latest blog post (gatsbyjs#4092) * [www] Fix quotes, fixes „Invalid date“ of latest blog post * Fix typo * Auto-deploy GraphQL docker image (gatsbyjs#4079) * Push image to docker hub when master is tagged like `gatsby@` * Build image on any commit to master (that isn't a PR merge) * Restore tiff option but without force option defaulting to true (gatsbyjs#4094) * Publish - [email protected] - [email protected] * Add Beach Hut Poole to Site Showcase (gatsbyjs#4106) * Add gatsby-starter-redux to gatsby-starters (gatsbyjs#4098) * Catch and exit if someone mistakenly puts their gatsby-config.js in the src directory fixes gatsbyjs#2674 (gatsbyjs#4101) * Publish - [email protected]

m-allanson force-pushed the search-home-page branch from b926fb4 to ad1e109 Compare January 23, 2018 12:37

m-allanson force-pushed the search-home-page branch from ad1e109 to 42c20b2 Compare February 1, 2018 21:46

m-allanson changed the title ~~[www] WIP: add search input to home page~~ [www] add search input to home page Feb 1, 2018

m-allanson added 5 commits February 2, 2018 20:53

Experiment adding search input to home page

965cb78

Prettier

5025f3a

Comment unused imports

14279a8

Display social icons when viewport is wide enough

c1b25ba

Use alternate colours at Hd breakpoint on home page

5b2c50b

m-allanson force-pushed the search-home-page branch from 42c20b2 to 5b2c50b Compare February 2, 2018 20:55

KyleAMathews merged commit 7588004 into gatsbyjs:master Feb 2, 2018

m-allanson deleted the search-home-page branch February 3, 2018 07:54

m-allanson mentioned this pull request Feb 3, 2018

[www] Add search form to home page #3603

Closed

snyk-bot mentioned this pull request Aug 18, 2021

[Snyk] Security upgrade webpack-dev-server from 3.11.2 to 4.0.0 Xtuden-com/gatsby#788

Open

This was referenced Aug 18, 2021

[Snyk] Security upgrade webpack-dev-server from 3.11.2 to 4.0.0 ajesse11x/gatsby#788

Open

[Snyk] Security upgrade webpack-dev-server from 3.11.2 to 4.0.0 saurabharch/gatsby#790

Open

saurabharch mentioned this pull request May 13, 2022

[Snyk] Fix for 1 vulnerabilities saurabharch/gatsby#1332

Open

harunpehlivan mentioned this pull request May 13, 2022

[Snyk] Fix for 1 vulnerabilities harunpehlivan/gatsby#1000

Open

ajesse11x mentioned this pull request May 13, 2022

[Snyk] Fix for 1 vulnerabilities ajesse11x/gatsby#1280

Open

kaocher82 mentioned this pull request May 13, 2022

[Snyk] Fix for 1 vulnerabilities Xtuden-com/gatsby#1951

Open

philipedin mentioned this pull request May 13, 2022

[Snyk] Fix for 1 vulnerabilities philipedin/gatsby#1077

Open

saurabharch mentioned this pull request Apr 28, 2023

[Snyk] Fix for 8 vulnerabilities saurabharch/gatsby#2051

Open

ajesse11x mentioned this pull request Jun 21, 2023

[Snyk] Fix for 1 vulnerabilities ajesse11x/gatsby#2073

Open

saurabharch mentioned this pull request Nov 27, 2023

[Snyk] Fix for 9 vulnerabilities saurabharch/gatsby#2383

Open

ajesse11x mentioned this pull request Nov 29, 2023

[Snyk] Fix for 9 vulnerabilities ajesse11x/gatsby#2220

Open

philipedin mentioned this pull request Mar 22, 2024

[Snyk] Fix for 1 vulnerabilities philipedin/gatsby#1586

Open

ajesse11x mentioned this pull request Mar 22, 2024

[Snyk] Fix for 1 vulnerabilities ajesse11x/gatsby#2621

Open

saurabharch mentioned this pull request Mar 23, 2024

[Snyk] Fix for 1 vulnerabilities saurabharch/gatsby#2886

Open

saurabharch mentioned this pull request May 13, 2024

[Snyk] Fix for 2 vulnerabilities saurabharch/gatsby#2917

Open

ajesse11x mentioned this pull request May 14, 2024

[Snyk] Fix for 2 vulnerabilities ajesse11x/gatsby#2705

Open

ajesse11x mentioned this pull request May 22, 2024

[Snyk] Fix for 2 vulnerabilities ajesse11x/gatsby#2736

Open

saurabharch mentioned this pull request May 22, 2024

[Snyk] Fix for 2 vulnerabilities saurabharch/gatsby#2975

Open

philipedin mentioned this pull request May 23, 2024

[Snyk] Security upgrade webpack-dev-server from 1.16.5 to 4.0.0 philipedin/gatsby#1648

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[www] add search input to home page #3662

[www] add search input to home page #3662

m-allanson commented Jan 23, 2018

gatsbybot commented Jan 23, 2018

gatsbybot commented Jan 23, 2018 •

edited

Loading

KyleAMathews commented Jan 23, 2018

KyleAMathews commented Jan 23, 2018

m-allanson commented Jan 23, 2018 •

edited

Loading

m-allanson commented Jan 23, 2018

KyleAMathews commented Jan 23, 2018

m-allanson commented Feb 1, 2018

KyleAMathews commented Feb 1, 2018

KyleAMathews commented Feb 2, 2018

m-allanson commented Feb 2, 2018

KyleAMathews commented Feb 2, 2018

KyleAMathews commented Feb 2, 2018

fk commented Feb 3, 2018

m-allanson commented Feb 3, 2018

[www] add search input to home page #3662

[www] add search input to home page #3662

Conversation

m-allanson commented Jan 23, 2018

gatsbybot commented Jan 23, 2018

gatsbybot commented Jan 23, 2018 • edited Loading

KyleAMathews commented Jan 23, 2018

KyleAMathews commented Jan 23, 2018

m-allanson commented Jan 23, 2018 • edited Loading

m-allanson commented Jan 23, 2018

KyleAMathews commented Jan 23, 2018

m-allanson commented Feb 1, 2018

KyleAMathews commented Feb 1, 2018

KyleAMathews commented Feb 2, 2018

m-allanson commented Feb 2, 2018

KyleAMathews commented Feb 2, 2018

KyleAMathews commented Feb 2, 2018

fk commented Feb 3, 2018

m-allanson commented Feb 3, 2018

gatsbybot commented Jan 23, 2018 •

edited

Loading

m-allanson commented Jan 23, 2018 •

edited

Loading