Revert "Enable filtering on linked nodes" #3613
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
|
My bad, I've totally overseen this case. Any suggestion could be used to prevent this? |
|
Deploy preview for gatsbygram ready! Built with commit fdf16dd |
|
Deploy preview for gatsbygram ready! Built with commit ee468f2 |
|
Missed some of my explanation — also part of the problem with the PR is you're trying to infer the input schema from one sample (the linked one) where what we want is to extract field examples from all instances of that node type Any random node might be missing some fields. Those field examples should then be filtered to remove any links back to the original node. We could recurse down through links but that could get expensive. Perhaps just remove all further links from linked nodes. We should also cache the extracted fields / node type as those are somewhat expensive to generate and this PR will mean more extractions. |
jastack
pushed a commit
to jastack/gatsby
that referenced
this pull request
Jan 24, 2018
* Revert "Fix images disappearing from rendered markdown files (gatsbyjs#3612)" This reverts commit 01022ab. * Revert "Bundle Netlify CMS styles (gatsbyjs#3611)" This reverts commit d19ec31. * Revert "Publish" This reverts commit 53f66a4. * Revert "Update comment" This reverts commit 2b22c2c. * Revert "Enable filtering on linked nodes (gatsbyjs#3600)" This reverts commit 7120e5a.
alvinthen
added a commit
to alvinthen/gatsby
that referenced
this pull request
Jan 25, 2018
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
KyleAMathews
pushed a commit
that referenced
this pull request
Feb 8, 2018
* ✨ 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
KyleAMathews
added a commit
that referenced
this pull request
Feb 15, 2018
* Revert "Update gatsby-browser.js (#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (#3717) * Publish - gatsby-plugin-no-sourcemaps@1.0.0 * 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 - gatsby-plugin-netlify@1.0.16 - gatsby-plugin-no-sourcemaps@1.0.1 - gatsby-transformer-remark@1.7.30 - gatsby@1.9.170 * 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 - gatsby-link@1.6.35 - gatsby@1.9.171 * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (#3735) * Publish - gatsby-cli@1.1.32 - gatsby@1.9.172 * 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 - gatsby-plugin-no-sourcemaps@1.0.2 - gatsby-plugin-typography@1.7.13 - gatsby-source-drupal@2.0.17 - gatsby-source-filesystem@1.5.16 - gatsby-source-wordpress@2.0.52 - gatsby@1.9.173 * [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 - gatsby-cli@1.1.33 - gatsby-plugin-netlify@1.0.17 - gatsby@1.9.174 * 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 - gatsby-plugin-google-analytics@1.0.17 - gatsby-plugin-twitter@1.0.16 - gatsby-react-router-scroll@1.0.9 - gatsby@1.9.175 * [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 - gatsby-cli@1.1.34 - gatsby-link@1.6.36 - gatsby-source-contentful@1.3.35 - gatsby@1.9.176 * 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 - gatsby-plugin-less@1.1.1 - gatsby-source-contentful@1.3.36 - gatsby@1.9.177 * 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 - gatsby-plugin-less@1.1.2 - gatsby@1.9.178 * 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 - gatsby-plugin-less@1.1.3 - gatsby-react-router-scroll@1.0.10 - gatsby-remark-copy-linked-files@1.5.26 - gatsby-source-drupal@2.0.18 - gatsby-source-filesystem@1.5.17 - gatsby-source-wordpress@2.0.53 - gatsby@1.9.179 * 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 - gatsby-image@1.0.35 - gatsby-plugin-less@1.1.4 - gatsby-plugin-sitemap@1.2.12 - gatsby-source-contentful@1.3.37 - gatsby-source-drupal@2.0.19 - gatsby-source-filesystem@1.5.18 - gatsby-source-wordpress@2.0.54 - gatsby-transformer-sharp@1.6.18 - gatsby@1.9.180 * 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 - gatsby-cli@1.1.35 - gatsby-transformer-screenshot@1.0.1 - gatsby@1.9.181 * [gatsby-plugin-feed] Fix missing colon in Readme (#3872) * Revert "Use HTTPS over git:// when cloning starters (#3820)" (#3876) This reverts commit 8261ac3. * Publish - gatsby-cli@1.1.36 - gatsby-plugin-feed@1.3.17 - gatsby@1.9.182 * use simple https to clone starters (#3875) * Publish - gatsby-cli@1.1.37 - gatsby@1.9.183 * [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 - gatsby-plugin-netlify-cms@1.0.6 - gatsby-remark-images@1.5.42 - gatsby@1.9.184 * Fix typo (#3899) * update prismjs-language-dependencies.js (#3898) * Publish - gatsby-remark-embed-snippet@1.0.7 - gatsby-remark-prismjs@1.2.13 * 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 - gatsby-remark-embed-snippet@1.0.8 - gatsby-remark-images@1.5.43 - gatsby-remark-prismjs@1.2.14 - gatsby-transformer-remark@1.7.31 * 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 - gatsby@1.9.185 * 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 <vlad@vladpasculescu.com> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - gatsby-cli@1.1.38 - gatsby@1.9.186 * 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 - gatsby@1.9.187 * Return a never to be resolved promise to prevent development server from exiting early fixes #3932 (#3933) * Publish - gatsby-cli@1.1.39 - gatsby@1.9.188 * 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 - gatsby@1.9.189 * 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 - gatsby@1.9.190 * Add LaserTime Clinic website to Readme (#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (#3952) * Publish - gatsby@1.9.191 * type inferring - handle array of Date objects (#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - gatsby@1.9.192 * 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 - gatsby-plugin-google-analytics@1.0.18 - gatsby@1.9.193 * 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 - gatsby-1-config-css-modules@1.0.9 - gatsby-cli@1.1.40 - gatsby-dev-cli@1.2.11 - gatsby-image@1.0.36 - gatsby-link@1.6.37 - gatsby-module-loader@1.0.10 - gatsby-plugin-aphrodite@1.0.7 - gatsby-plugin-canonical-urls@1.0.13 - gatsby-plugin-catch-links@1.0.16 - gatsby-plugin-coffeescript@1.4.10 - gatsby-plugin-create-client-paths@1.0.5 - gatsby-plugin-cxs@1.0.7 - gatsby-plugin-emotion@1.1.12 - gatsby-plugin-feed@1.3.18 - gatsby-plugin-glamor@1.6.12 - gatsby-plugin-glamorous@1.0.7 - gatsby-plugin-google-analytics@1.0.19 - gatsby-plugin-google-tagmanager@1.0.14 - gatsby-plugin-jss@1.5.11 - gatsby-plugin-less@1.1.5 - gatsby-plugin-lodash@1.0.9 - gatsby-plugin-manifest@1.0.14 - gatsby-plugin-netlify-cms@1.0.7 - gatsby-plugin-netlify@1.0.18 - gatsby-plugin-no-sourcemaps@1.0.3 - gatsby-plugin-nprogress@1.0.12 - gatsby-plugin-offline@1.0.14 - gatsby-plugin-postcss-sass@1.0.17 - gatsby-plugin-preact@1.0.16 - gatsby-plugin-react-css-modules@1.0.13 - gatsby-plugin-react-helmet@2.0.5 - gatsby-plugin-react-next@1.0.9 - gatsby-plugin-remove-trailing-slashes@1.0.5 - gatsby-plugin-sass@1.0.17 - gatsby-plugin-sharp@1.6.28 - gatsby-plugin-sitemap@1.2.13 - gatsby-plugin-styled-components@2.0.6 - gatsby-plugin-styled-jsx@2.0.3 - gatsby-plugin-styletron@1.0.12 - gatsby-plugin-stylus@1.1.15 - gatsby-plugin-twitter@1.0.17 - gatsby-plugin-typescript@1.4.16 - gatsby-plugin-typography@1.7.14 - gatsby-react-router-scroll@1.0.11 - gatsby-remark-autolink-headers@1.4.12 - gatsby-remark-code-repls@1.0.9 - gatsby-remark-copy-linked-files@1.5.27 - gatsby-remark-custom-blocks@1.0.3 - gatsby-remark-embed-snippet@1.0.9 - gatsby-remark-images@1.5.44 - gatsby-remark-katex@1.0.11 - gatsby-remark-prismjs@1.2.15 - gatsby-remark-responsive-iframe@1.4.17 - gatsby-remark-smartypants@1.4.11 - gatsby-source-contentful@1.3.38 - gatsby-source-drupal@2.0.20 - gatsby-source-faker@1.0.2 - gatsby-source-filesystem@1.5.19 - gatsby-source-hacker-news@1.0.10 - gatsby-source-lever@1.0.8 - gatsby-source-medium@1.0.12 - gatsby-source-mongodb@1.5.14 - gatsby-source-wordpress-com@1.0.6 - gatsby-source-wordpress@2.0.55 - gatsby-transformer-csv@1.3.8 - gatsby-transformer-documentationjs@1.4.9 - gatsby-transformer-docx@1.0.6 - gatsby-transformer-excel@1.0.4 - gatsby-transformer-hjson@1.0.3 - gatsby-transformer-javascript-static-exports@1.3.9 - gatsby-transformer-json@1.0.15 - gatsby-transformer-pdf@1.0.6 - gatsby-transformer-pdfimages@1.0.5 - gatsby-transformer-react-docgen@1.0.13 - gatsby-transformer-remark@1.7.32 - gatsby-transformer-screenshot@1.0.2 - gatsby-transformer-sharp@1.6.19 - gatsby-transformer-toml@1.1.8 - gatsby-transformer-xml@1.0.12 - gatsby-transformer-yaml@1.5.15 - gatsby@1.9.194 - graphql-skip-limit@1.0.10 * [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 - gatsby-remark-katex@1.0.12 - gatsby-transformer-react-docgen@1.0.14 - gatsby@1.9.195 * 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 - gatsby-image@1.0.37 - gatsby@1.9.196 * 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 - gatsby@1.9.197 * 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 - gatsby-source-mongodb@1.5.15 - gatsby-source-wordpress@2.0.56 - gatsby-transformer-javascript-frontmatter@1.0.1 - gatsby-transformer-javascript-static-exports@1.3.10 - gatsby@1.9.198 * 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 - gatsby@1.9.199 * 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
KyleAMathews
added a commit
that referenced
this pull request
Feb 17, 2018
* Revert "Update gatsby-browser.js (#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (#3717) * Publish - gatsby-plugin-no-sourcemaps@1.0.0 * 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 - gatsby-plugin-netlify@1.0.16 - gatsby-plugin-no-sourcemaps@1.0.1 - gatsby-transformer-remark@1.7.30 - gatsby@1.9.170 * 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 - gatsby-link@1.6.35 - gatsby@1.9.171 * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (#3735) * Publish - gatsby-cli@1.1.32 - gatsby@1.9.172 * 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 - gatsby-plugin-no-sourcemaps@1.0.2 - gatsby-plugin-typography@1.7.13 - gatsby-source-drupal@2.0.17 - gatsby-source-filesystem@1.5.16 - gatsby-source-wordpress@2.0.52 - gatsby@1.9.173 * [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 - gatsby-cli@1.1.33 - gatsby-plugin-netlify@1.0.17 - gatsby@1.9.174 * 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 - gatsby-plugin-google-analytics@1.0.17 - gatsby-plugin-twitter@1.0.16 - gatsby-react-router-scroll@1.0.9 - gatsby@1.9.175 * [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 - gatsby-cli@1.1.34 - gatsby-link@1.6.36 - gatsby-source-contentful@1.3.35 - gatsby@1.9.176 * 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 - gatsby-plugin-less@1.1.1 - gatsby-source-contentful@1.3.36 - gatsby@1.9.177 * 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 - gatsby-plugin-less@1.1.2 - gatsby@1.9.178 * 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 - gatsby-plugin-less@1.1.3 - gatsby-react-router-scroll@1.0.10 - gatsby-remark-copy-linked-files@1.5.26 - gatsby-source-drupal@2.0.18 - gatsby-source-filesystem@1.5.17 - gatsby-source-wordpress@2.0.53 - gatsby@1.9.179 * 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 - gatsby-image@1.0.35 - gatsby-plugin-less@1.1.4 - gatsby-plugin-sitemap@1.2.12 - gatsby-source-contentful@1.3.37 - gatsby-source-drupal@2.0.19 - gatsby-source-filesystem@1.5.18 - gatsby-source-wordpress@2.0.54 - gatsby-transformer-sharp@1.6.18 - gatsby@1.9.180 * 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 - gatsby-cli@1.1.35 - gatsby-transformer-screenshot@1.0.1 - gatsby@1.9.181 * [gatsby-plugin-feed] Fix missing colon in Readme (#3872) * Revert "Use HTTPS over git:// when cloning starters (#3820)" (#3876) This reverts commit 8261ac3. * Publish - gatsby-cli@1.1.36 - gatsby-plugin-feed@1.3.17 - gatsby@1.9.182 * use simple https to clone starters (#3875) * Publish - gatsby-cli@1.1.37 - gatsby@1.9.183 * [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 - gatsby-plugin-netlify-cms@1.0.6 - gatsby-remark-images@1.5.42 - gatsby@1.9.184 * Fix typo (#3899) * update prismjs-language-dependencies.js (#3898) * Publish - gatsby-remark-embed-snippet@1.0.7 - gatsby-remark-prismjs@1.2.13 * 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 - gatsby-remark-embed-snippet@1.0.8 - gatsby-remark-images@1.5.43 - gatsby-remark-prismjs@1.2.14 - gatsby-transformer-remark@1.7.31 * 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 - gatsby@1.9.185 * 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 <vlad@vladpasculescu.com> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - gatsby-cli@1.1.38 - gatsby@1.9.186 * 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 - gatsby@1.9.187 * Return a never to be resolved promise to prevent development server from exiting early fixes #3932 (#3933) * Publish - gatsby-cli@1.1.39 - gatsby@1.9.188 * 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 - gatsby@1.9.189 * 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 - gatsby@1.9.190 * Add LaserTime Clinic website to Readme (#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (#3952) * Publish - gatsby@1.9.191 * type inferring - handle array of Date objects (#3955) * inferring types: handle array of Date objects * add tests for inferring arrays of Date objects * Publish - gatsby@1.9.192 * 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 - gatsby-plugin-google-analytics@1.0.18 - gatsby@1.9.193 * 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 - gatsby-1-config-css-modules@1.0.9 - gatsby-cli@1.1.40 - gatsby-dev-cli@1.2.11 - gatsby-image@1.0.36 - gatsby-link@1.6.37 - gatsby-module-loader@1.0.10 - gatsby-plugin-aphrodite@1.0.7 - gatsby-plugin-canonical-urls@1.0.13 - gatsby-plugin-catch-links@1.0.16 - gatsby-plugin-coffeescript@1.4.10 - gatsby-plugin-create-client-paths@1.0.5 - gatsby-plugin-cxs@1.0.7 - gatsby-plugin-emotion@1.1.12 - gatsby-plugin-feed@1.3.18 - gatsby-plugin-glamor@1.6.12 - gatsby-plugin-glamorous@1.0.7 - gatsby-plugin-google-analytics@1.0.19 - gatsby-plugin-google-tagmanager@1.0.14 - gatsby-plugin-jss@1.5.11 - gatsby-plugin-less@1.1.5 - gatsby-plugin-lodash@1.0.9 - gatsby-plugin-manifest@1.0.14 - gatsby-plugin-netlify-cms@1.0.7 - gatsby-plugin-netlify@1.0.18 - gatsby-plugin-no-sourcemaps@1.0.3 - gatsby-plugin-nprogress@1.0.12 - gatsby-plugin-offline@1.0.14 - gatsby-plugin-postcss-sass@1.0.17 - gatsby-plugin-preact@1.0.16 - gatsby-plugin-react-css-modules@1.0.13 - gatsby-plugin-react-helmet@2.0.5 - gatsby-plugin-react-next@1.0.9 - gatsby-plugin-remove-trailing-slashes@1.0.5 - gatsby-plugin-sass@1.0.17 - gatsby-plugin-sharp@1.6.28 - gatsby-plugin-sitemap@1.2.13 - gatsby-plugin-styled-components@2.0.6 - gatsby-plugin-styled-jsx@2.0.3 - gatsby-plugin-styletron@1.0.12 - gatsby-plugin-stylus@1.1.15 - gatsby-plugin-twitter@1.0.17 - gatsby-plugin-typescript@1.4.16 - gatsby-plugin-typography@1.7.14 - gatsby-react-router-scroll@1.0.11 - gatsby-remark-autolink-headers@1.4.12 - gatsby-remark-code-repls@1.0.9 - gatsby-remark-copy-linked-files@1.5.27 - gatsby-remark-custom-blocks@1.0.3 - gatsby-remark-embed-snippet@1.0.9 - gatsby-remark-images@1.5.44 - gatsby-remark-katex@1.0.11 - gatsby-remark-prismjs@1.2.15 - gatsby-remark-responsive-iframe@1.4.17 - gatsby-remark-smartypants@1.4.11 - gatsby-source-contentful@1.3.38 - gatsby-source-drupal@2.0.20 - gatsby-source-faker@1.0.2 - gatsby-source-filesystem@1.5.19 - gatsby-source-hacker-news@1.0.10 - gatsby-source-lever@1.0.8 - gatsby-source-medium@1.0.12 - gatsby-source-mongodb@1.5.14 - gatsby-source-wordpress-com@1.0.6 - gatsby-source-wordpress@2.0.55 - gatsby-transformer-csv@1.3.8 - gatsby-transformer-documentationjs@1.4.9 - gatsby-transformer-docx@1.0.6 - gatsby-transformer-excel@1.0.4 - gatsby-transformer-hjson@1.0.3 - gatsby-transformer-javascript-static-exports@1.3.9 - gatsby-transformer-json@1.0.15 - gatsby-transformer-pdf@1.0.6 - gatsby-transformer-pdfimages@1.0.5 - gatsby-transformer-react-docgen@1.0.13 - gatsby-transformer-remark@1.7.32 - gatsby-transformer-screenshot@1.0.2 - gatsby-transformer-sharp@1.6.19 - gatsby-transformer-toml@1.1.8 - gatsby-transformer-xml@1.0.12 - gatsby-transformer-yaml@1.5.15 - gatsby@1.9.194 - graphql-skip-limit@1.0.10 * [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 - gatsby-remark-katex@1.0.12 - gatsby-transformer-react-docgen@1.0.14 - gatsby@1.9.195 * 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 - gatsby-image@1.0.37 - gatsby@1.9.196 * 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 - gatsby@1.9.197 * 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 - gatsby-source-mongodb@1.5.15 - gatsby-source-wordpress@2.0.56 - gatsby-transformer-javascript-frontmatter@1.0.1 - gatsby-transformer-javascript-static-exports@1.3.10 - gatsby@1.9.198 * 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 - gatsby@1.9.199 * 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 - gatsby-plugin-styled-components@2.0.7 - gatsby@1.9.200 * 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 - gatsby-plugin-sharp@1.6.29 - gatsby-remark-images@1.5.45 - gatsby-source-drupal@2.0.21 - gatsby-source-filesystem@1.5.20 - gatsby-source-wordpress@2.0.57 - gatsby@1.9.201 * [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 - gatsby-plugin-sharp@1.6.30 - gatsby-remark-images@1.5.46 * 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 - gatsby@1.9.202
calcsam
pushed a commit
that referenced
this pull request
Mar 6, 2018
* Support URLs that end in SemVer ranges (#3305) Fixes #3164. * page path defaults to '/' (#3325) * page path defaults to '/' * Add test * Use graymatter excerpt in gatsby-transformer-remark (#2883) * Check for graymatter excerpt Checks to see if there is a gray-matter excerpt before returning a pruned character count * Fix test Remove a variable that wasn't being used * Create page to describe excerpts * Update using-remark example * Remove package-lock.json * Remove console.log statements * Update copy Updates copy to be a bit more descriptive * Update header for example page * Begin stubbing out extend-node.js tests Created a basic framework for creating a markdown node via the onCreateNode function. This should be expanded to factor in the changes that occur in the setFieldsOnGraphQLNodeType function. * Add query test Adds a test that uses graphql to query a node with its excerpt * Regroup tests Regroups tests so that graphql queries and node tests are in their own groups * Fix linting errors Fixes linting errors that were causing issues on travisCI * Format * handles integer with valida date format correctly (#3461) * Upgrade style-loader to fix CSS modules issue (#3283) * Upgrade style-loader to 0.19.0 to fix webpack-contrib/style-loader#182 * Update to last version * format/bootstrap * Publish - gatsby-link@1.6.34 - gatsby-source-faker@1.0.0 - gatsby-transformer-remark@1.7.27 - gatsby@1.9.151 * Updated links for Glamor and Styled Components (#3462) * Updated links for Glamor and Styled Components * Update index.md * Update tutorial.js * Add link to the using-remark website * Don't create pages for test files (#3464) * Don't generate pages for test files * Use parsedPath.base instead of path * Add gatsby-source-behance to plugins list (#3465) * activated mergeLinkHeaders (#3463) * Add cache-control examples to caching docs page (#3468) * Publish - gatsby-plugin-netlify@1.0.13 - gatsby-transformer-remark@1.7.28 - gatsby@1.9.152 * Revert "Upgrade style-loader to fix CSS modules issue (#3283)" This reverts commit 834dcb8. A number of people were reporting that this broke the default starter in node 8 e.g. https://twitter.com/Lehanism/status/951397594953076737 * Publish - gatsby@1.9.153 * Fix Links Redirection (#3471) * Fix Links Redirection * Fix Glamor Link Redirection * Fix typo (#3470) * Update tutorial-links.yml * Cleanup Glamor / Styled Component mini-tutorials (#3474) * Cleanup Glamor / Styled Component mini-tutorials * Tweaks * Fix typo in building with components section (#3476) reusabilty => reusability * Fix typo (#3477) * Update Deploy Gatsby page - Gitlab Pages (#3482) * Update Deploy Gatsby page - Gitlab Pages Have made a few edits, mainly to include the Path Prefix plugin, which is needed when using Gitlab pages without a custom domain. This has basically been shamelessly copied from the Github pages example... Also did a bit of formatting. * fix typo * correct key behavior (#3483) * correct key behavior * remove trailing slash logic * remove adding new variable * Publish - gatsby-plugin-create-client-paths@1.0.2 - gatsby-react-router-scroll@1.0.8 - gatsby@1.9.154 * Add Strata starter (#3488) Add Strata starter to the list. * Use `_.isPlainObject` to prevent false Array positives (#3490) * Publish - gatsby-source-wordpress@2.0.43 * update styled-jsx dep in gatsby-plugin-styled-jsx (#3493) * update styled-jsx dep in gatsby-plugin-styled-jsx * move styled-jsx to peerDependencies in gatsby-plugin-styled-jsx * Publish - gatsby-plugin-styled-jsx@2.0.1 * gatsby-image docs (#3500) * Update CONTRIBUTING.md small typo * Update README.md typo fixes and additional section * Update awesome-gatsby.md * Update README.md * Easy edits based off of observing Eden go thru tutorials (#3501) A few typo corrections and clarified wording. There are more big changes to address later. * [gatsby] don't run service-workers outside of https or localhost (#3502) * [gatsby] don't run service-workers outside of https or localhost see: #3385 * add detail around running local changes to CONTRIBUTING.md * Update CONTRIBUTING.md * format * format * Publish - gatsby-image@1.0.32 - gatsby@1.9.155 * Properly use `withPrefix` in adding-images-fonts-files docs (#3503) I came across this while browsing through the documentation. The `withPrefix` import was left unused in the "escape hatch" example, which I'm pretty sure is not intentional. * Create new npm keyword for gatsby components (#3507) * Publish - gatsby-image@1.0.33 * Fix typo in docs (#3511) * Add Netlify CMS plugin, related docs (#3509) * add Netlify CMS plugin * add Netlify CMS guide * add Netlify to deploy docs * Update deploy-gatsby.md * Publish - gatsby-plugin-netlify-cms@1.0.1 * Fix clone instructions (#3514) * Publish - gatsby-plugin-netlify-cms@1.0.1 * Fix instructions for cloning the docs * Search and replace the hostname in URLs. (#3498) * Search and replace the hostname in URLs. #3450 * Fixed code styling issues * Missed backticks for the timers requirement * Updated readme with search and replace options * Removed async, wrapped json parse in a try catch and updated blacklist function * Updated search and replace api and updated documentation * Added logging for invalid search and replace option * make option more explicit, updated default value & removed redundant logging * Updated the variable name making it clearer * Add documentation on adding list of blog posts (#3510) * Add documentation on adding list of blog posts * Update adding-a-list-of-markdown-blog-posts.md * Import the component * [DOCS] Adding Markdown pages: Remove useless fields (#3517) * [DOCS] Adding Markdown pages: Remove useless fields * Update adding-markdown-pages.md * [DOCS] Links: Remove emphasis from implem stubs (#3518) * [DOCS] Links: Remove emphasis from implem stubs Some docs have been implemented but are still marked as stubs in the navigation drawer * Update doc-links.yaml * fix link (#3513) * Add missing comma in sitemap example (#3520) * Move inlined webpack manifest to the end of body element (#3519) * Adds email capture to bottom of blog (#3333) * Adds email capture to bottom of blog * Adds email capture to bottom of blog * Adds Mailchimp functionality * Refactors postEmailToMailchimp method, updates cc * updates rhythm css, installs & uses validator module * Fiddle with design * Fix `gatsby-plugin-nprogress` default options param (#3533) * Fix default `pluginOptions` parameter This PR fixes #3484 Correctly merge `defaultOptions` with `pluginOptions` * Indent `styles` template string correctly * Change default * Format * Publish - gatsby-plugin-netlify-cms@1.0.2 - gatsby-plugin-nprogress@1.0.10 - gatsby-plugin-sitemap@1.2.10 - gatsby-source-wordpress@2.0.44 - gatsby@1.9.156 * Don't use internal name when reporting there's an error in gatsby-node.js fixes #2945 (#3536) * Don't use internal name when reporting there's an error in gatsby-node.js fixes #2945 * Move var initialization into tighter scope * can I code??? * Publish - gatsby@1.9.157 * Add Developer Ecosystem to websites (#3540) * Removes words like 'simple' & 'easy' from docs/www (#3523) * Removes words like 'simple' & 'easy' from docs/www * Additional optimizations * Update gatsby-v1.md * Update add-404-page.md * Update gatsby-style-guide.md * Update styled-components.md * Update index.md * Update index.md * cpinnix/verious starter (#3543) * Added verious-boilerplate to gatsby starters documentation. * Added Charles Pinnix Website and Verious to Showcase. * gatsby-plugin-sharp: Remove warning for resolutions when requested width and image width are equal (#3537) * Add to instructions that you need gatsby-plugin-sharp fixes #3545 (#3547) * Update katex package to 0.8.3 (#3548) * add unique titles to docs, tutorial, blog (#3550) * Fix typo in KaTeX usage example (#3549) * format * Publish - gatsby-plugin-netlify@1.0.14 - gatsby-plugin-sharp@1.6.25 - gatsby-remark-embed-snippet@1.0.6 - gatsby-remark-images@1.5.37 - gatsby-remark-katex@1.0.9 - gatsby-remark-prismjs@1.2.12 * [www] Fix <link rel=„author“> href (#3555) * [www] Fix email-capture-form cross browser issues (#3553) * pull shared <input>/<button> styles into constant * add default background color * add placeholder styles * use Futura instead of Spectral for form inputs* help Safari rendering <button> and <input> at equal height (tested in v11.0.2) * add focus styles * add focus styles to CtaButton * Add docs page with overview of Gatsby's usage of GraphQL (#3557) * Add docs page with overview of Gatsby's usage of GraphQL * Add missing word * Debugging HTML Builds - fix copy&paste error (#3565) the point of the code-demo is that if we wrap the module it does not fail * Update outdated snapshot (#3566) * Update readme with demo link (#3573) * Move script loader after webpack manifest (#3569) This should ensure that when any external scripts are loaded using script loader, the webpack manifest is already present. * Publish - gatsby-remark-katex@1.0.10 - gatsby@1.9.158 * Added 'Steve Meredith's Portfolio' to 'Showcase' (#3576) * City of Boston case study blog post (#3583) * boston blog post * blog v2 * Add Put.io landing page to showcase (#3580) * Allow arrays with more than one file path & ignore empty strings (#3577) * Publish - gatsby@1.9.159 * Add search form to site (#3421) * Add search form to site header * Prevent sidebar from overlapping search results * Override default search result styles * Reduce size of mask image * Prettier * Add a class name for the DocSearch crawlers As mentioned in the DocSearch signup message: #3097 (comment) * Disable DocSearch's debug mode * Capture default navigation events, replace with client-side navigation * Add a second identifier class for DocSearch * Improve mobile styles * Improve styling - Increase specificity so styles work in production build - Tidy up layout at medium and small breakpoints - Prettier * Load external CSS after document body * Some minor edits (#3586) * Some minor edits I also think it could be cool to explain just a few use cases that answer this question: "Why is GraphQL so cool?" I also expected to see code examples for image stuff. Also, a random thing about colons that I learned last year is this: a full sentence must precede the colon :) * Tweak * Add sample code showing off gatsby-image + image processing to query with GraphQL page (#3589) * Add sample code showing off gatsby-image + image processing to query with GraphQL page * Update querying-with-graphql.md * Update README.md * Improve documentation for createParentChildLink (#3594) * Improve documentation for createParentChildLink * Format * edit * Some updates to the awesome gatsby page (#3595) * Add Ryan Wiemer's Portfolio to the showcase (#3578) * Updated Plugins.md (#3593) Added Gatsby Directus Source Plugin * [www] Add gatsby-plugin-postcss-sass (#3590) * [www] Improve docsearch UI for small devices (#3597) * [www] Improve docsearch for small devices * ditch css.global(…) and instead use css.insert() for all CSS overriding/building upon the stock docsearch.css – couldn’t figure out any advantages in using css.global over css.insert() * full-width result list items and calmer subcategory titles for small devices * „purpelize“ UI and replace a few more stock colors with equivalents from utils/presets * slightly wider result dropdown for desktop and above * remove result dropdown outer padding and fiddle with whitespace * debug:false * Add section why GraphQL is *cool* (#3606) * [www] Increase navigation z-index (#3599) Prevent the author link on blog post cards from showing above the new docsearch dropdown. * Added `gatsby-plugin-bugherd` to community plugins (#3605) * [gatsby-source-contentful] Delete original link regardless of ID validity (#3592) * wip * [gatsby-source-contentful] Delete original link regardless of presence of resolvable ID * Publish - gatsby-image@1.0.34 - gatsby-source-contentful@1.3.32 - gatsby@1.9.160 * Create new page docs/creating-hybrid-pages-with-static-and-dynamic-components.md (#3579) * Update docs/creating-and-modifying-pages.md to expand on the use of client-only routes to create a hybrid or "app-shell" Gatsby app * + Split hybrid page docs into its own page and update linked pages * Update creating-and-modifying-pages.md * Update and rename creating-hybrid-pages-with-static-and-dynamic-components.md to building-apps-with-gatsby * Update creating-and-modifying-pages.md * Rename building-apps-with-gatsby to building-apps-with-gatsby.md * Update README.md * Update building-apps-with-gatsby.md * Add link to new docs page * Enable filtering on linked nodes (#3600) Add support to filter on linked nodes. Close #3190 * Update comment * Publish - gatsby-plugin-create-client-paths@1.0.3 - gatsby@1.9.161 * Bundle Netlify CMS styles (#3611) * define webpack loader.exclude with array for extensibility * generate separate CSS bundle for Netlify CMS plugin * Fix images disappearing from rendered markdown files (#3612) * Fix images disappearing from rendered markdown files Fixes #3608 * Revert invalid indentation changes * Revert "Enable filtering on linked nodes" (#3613) * Revert "Fix images disappearing from rendered markdown files (#3612)" This reverts commit 01022ab. * Revert "Bundle Netlify CMS styles (#3611)" This reverts commit d19ec31. * Revert "Publish" This reverts commit 53f66a4. * Revert "Update comment" This reverts commit 2b22c2c. * Revert "Enable filtering on linked nodes (#3600)" This reverts commit 7120e5a. * Publish - gatsby-plugin-netlify-cms@1.0.3 - gatsby-remark-images@1.5.38 - gatsby@1.9.162 * Add yerevancoder (#3598) * Fix gatsby-remark-image (#3620) * Publish - gatsby-plugin-netlify-cms@1.0.4 - gatsby-remark-images@1.5.39 - gatsby@1.9.163 * WordPress Media Download Basic Auth Fix (#3614) * WordPress Media Download Basic Auth Fix * format * Publish - gatsby-source-drupal@2.0.13 - gatsby-source-filesystem@1.5.12 - gatsby-source-wordpress@2.0.45 * Set default auth object * Publish - gatsby-source-drupal@2.0.14 - gatsby-source-filesystem@1.5.13 - gatsby-source-wordpress@2.0.46 * Improve checks on authentication so have wiggle room in future * Publish - gatsby-source-drupal@2.0.15 - gatsby-source-filesystem@1.5.14 - gatsby-source-wordpress@2.0.47 * Fix passing auth info to createRemoteFileNode (#3628) * Fix copying "dev-404-page.js" to the cache folder on Windows (#3627) * Fix images disappearing from rendered markdown files Fixes #3608 * Revert invalid indentation changes * Fix copying "dev-404-page.js" to the cache folder on Windows Fixes #2819 * Fix snapshot tests * Revert invalid improper snapshot test modification * Publish - gatsby-source-wordpress@2.0.48 * Publish - gatsby-source-wordpress@2.0.49 - gatsby@1.9.164 * Tweak copy on the new building apps with gatsby docs page (#3631) * Added gatsby-starter-lumen * Add link to Gentics Mesh source community plugin (#3629) * Add section about deploying with now to the docs (#3641) * Add section to the deploy docs page for deploying to now * Add section to the deploy docs page for deploying to now * Add install code snippet * Update deploy-gatsby.md * docs: gatsby config options (#3095) (#3646) * index.md (#3638) * index.md I am not the only one who got this problem. I think some other junior leaner will do the same. My English is poor.If the idea is good, please change it to correct spelling and grammar. here is the question link: #1739 * Update index.md * All the author info for Pierre (#3651) I'm pretty sure I need to update the actual blog post. It's not in master branch on my computer yet, so will just edit it via web * Strapi blog post content (#3618) * Strapi blog post content Avatar and bio still coming, will make those edits and edit yaml later * Updated author info Also I just realized that the images in here might not work if we don't have original files in the directory. Is this true, @kylemathews? * Add tutorial series links to docs (#3634) * Add tutorial series links to docs * Update awesome-gatsby.md * [WIP] Update Gatsbygram to make it work with current (unofficial) JSON API. (#3349) * Update Gatsbygram to make it work with current (unofficial) JSON API. * Revert back to previous data structure; add case study URL to README. * Contributing (#3619) * Contributing Not sure if "adding unit or functional tests" makes sense. Took it from webpack example. Also added your hierarchy of helpfulness under ### special note on issues. Don't know if the sentence introducing them is the best advice... Also check the plugin naming convention. Hope I'm getting the header levels right here. There is some overlap here with the Gatsby style guide. I've got it on a to-do list to think through division of information between the two docs * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Update CONTRIBUTING.md * [gatsby-transformer-remark] Add `htmlAst` field (#3596) This implements a GraphQL field that presents the rehype AST as JSON, allowing for this information to be consumed from a page template and presented dynamically. * Publish - gatsby-transformer-remark@1.7.29 * Update building-apps-with-gatsby.md (#3653) * fix extract-text--webpack-plugin instance reuse errors (#3652) * Publish - gatsby@1.9.165 * Minor change to tutorial part four index.md (#3649) * Minor change to tutorial part four index.md Changed one liner 2 steps to <ol> style. More readable. * Update index.md * Added deploy task to gh-pages in Org pages (#3642) Added the task to deploy to Github Pages in Organizations pages like organization.github.io * Added community plugin: gatsby-plugin-pathdata (#3644) * Add gatsby-starter-strict (#3645) * blog: add getting started with gatsby and wordpress (#3647) * blog: add getting started with gatsby and wordpress * Make links local to gatsbyjs.org + a few other tweaks * [www] Search shortcut (#3654) * Add keyboard shortcut for focussing the search input * Blur input on result selection * Remove note about their being more parts to the tutorial (#3655) * Remove note about their being more parts to the tutorial We'll ship more stuff when we do. No reason to make it sound less than useful as it is. * format * Add images in Strapi tutorial (#3660) * Add images in Strapi tutorial * Remove package-lock.json files * added gatsby ^1.0.0 as a peer dependency for all plugins (#3637) * README showcase update (#3661) * updated README with two of my gatsbyjs projects. I hope this alright, if not I totally understand * Updated README fix space issue * Add gatsby-starter-portfolio-emilia (#3664) Also grouped both starters into one bulletpoint (as talked about on Discord) and changed some minor stuff. * [gatsby-source-medium] fetch users and publications (#3623) * Add support for fetching a users payload along with publications from Medium * Update gatsby-source-medium readme, add note for @ for usernames * Undo any changes to `links` variable * Publish - gatsby-plugin-aphrodite@1.0.6 - gatsby-plugin-canonical-urls@1.0.12 - gatsby-plugin-catch-links@1.0.15 - gatsby-plugin-coffeescript@1.4.9 - gatsby-plugin-create-client-paths@1.0.4 - gatsby-plugin-cxs@1.0.6 - gatsby-plugin-emotion@1.1.11 - gatsby-plugin-feed@1.3.16 - gatsby-plugin-glamor@1.6.11 - gatsby-plugin-glamorous@1.0.6 - gatsby-plugin-google-analytics@1.0.16 - gatsby-plugin-google-tagmanager@1.0.13 - gatsby-plugin-jss@1.5.10 - gatsby-plugin-less@1.0.9 - gatsby-plugin-lodash@1.0.8 - gatsby-plugin-manifest@1.0.13 - gatsby-plugin-netlify-cms@1.0.5 - gatsby-plugin-netlify@1.0.15 - gatsby-plugin-nprogress@1.0.11 - gatsby-plugin-offline@1.0.13 - gatsby-plugin-postcss-sass@1.0.16 - gatsby-plugin-preact@1.0.15 - gatsby-plugin-react-css-modules@1.0.12 - gatsby-plugin-react-helmet@2.0.4 - gatsby-plugin-react-next@1.0.8 - gatsby-plugin-remove-trailing-slashes@1.0.4 - gatsby-plugin-sass@1.0.16 - gatsby-plugin-sharp@1.6.26 - gatsby-plugin-sitemap@1.2.11 - gatsby-plugin-styled-components@2.0.5 - gatsby-plugin-styled-jsx@2.0.2 - gatsby-plugin-styletron@1.0.11 - gatsby-plugin-stylus@1.1.14 - gatsby-plugin-twitter@1.0.15 - gatsby-plugin-typescript@1.4.13 - gatsby-plugin-typography@1.7.11 - gatsby-remark-images@1.5.40 - gatsby-source-medium@1.0.10 * [gatsby-source-contentful] Make base64 query to field-level to speed up asset queries (#3617) * [gatsby-source-contentful] Add withBase64 option to speed up image queries * Revert "[gatsby-source-contentful] Add withBase64 option to speed up image queries" This reverts commit bb080f7. * remove base64 from resolveResponsiveResolution * create base64 resolver * update sizes, reset resize to original state * update tests * update resize and tests * Publish - gatsby-source-contentful@1.3.33 * show help and recommend when the command is wrong (#3668) * Fix gatsby-starter-portfolio-emilia PR (#3667) Seems like "Features" or something other is messing up the indentation and therefore messing up the whole idea of two sub-entries. So I just did two separate entries now. * Add Flooring Factories Outlets to Showcase (#3666) Added a website made for a client... built with gatsby / netlify :) * Publish - gatsby-cli@1.1.29 - gatsby@1.9.166 * Add a podcast website/player to the showcase (#3672) * [www] Update/consolidate palette, monogram and logo, favicons (#3639) * #744c9e/116,76,158 -> #9966cc/102, 51, 153 (rebeccapurple) * [WIP] Consolidate palette * Ditch B100 in favor of B200 * Neutral diagram stripe color at least for now * Fussing around with saturation * Adjustting hues (still WIP ;-)) * Roll back all palette colors but brand/„B700“ * Throw in chroma.js, output presets.B*, chroma.js palette at /colors * B200 -> B100 * B300 -> B200 * colors.b[0] -> B100 * components/diagram „box“ border * layouts/index sidebar border-right * Grab chroma-js from npm now that 1.3.6 is published * Add redrawn monogram and logo (monogram + wordmark) * remove gatsby-calm.svg for now – was only used on the blog page, where we’re for now using the regular monogram * remove gatsby-negative.png, not in use – will regenerate the favicons that were probably based on this and add them ASAP * remove gatsby-positive.svg, unused * rename gatsby-negative.svg to monogram.svg, update it with the redrawn version * replace logo and <h1> wordmark in components/navigation with the newly added logo.svg * Update favicons * fix apple-touch-icon.png, which had a transparent background which iOS resolves to black which looks 😒 * fix non-anti-aliased edges in all favicons * add a white background for the „G and chopped edge“ shape of the favicon which was transparent before * fix Safari pinned tab color * Add hex2rgba, remove presets.shadowColor (matches presets.B500) * Inherit text color * Move colors from presets to colors * Remove orange logo * Bump favicon.ico * Optimize favicons, update Windows tile icons * Update manifest theme/background_color * Remove some leftover anchors; invert logo for iOS, Windows tile * Add Windows tile browserconfig.xml * Oops * Remove chroma (…), back to descriptive color names * Make presets.calm pass WCAG AA * Fix icon colors * Remove presets.brandDark * Add colors.gray * :D * Make presets.calm pass WCAG AA again * rebeccapurple links in blog articles * Fix logo offset * Ditch colors.brand, add colors.ui, don’t litter colors in presets 🙄 * rename `brand` to `gatsby` * expose `utils/colors` at `presets.colors` * move UI colors to `colors.ui` * add colors.success, colors.warning * Update logo wordmark, optimize SVGs * Update building-apps-with-gatsby.md * Add plugins.js and searchbar-body.js for searching and displaying gatsby plugins * Remove unneccesary css * Removed package-lock.json and renamed plugins.js to packages.js * Add algolia-npm search and url syncing * Add background color when plugin selected * Fix doubling-up layout bug, add border to hits component, add margin to text in packages * Remove unnecessary dependencies from package.json * Remove withUrlSync.js * Change Algolia link from Link to a tag * Add gatsby-component as keyword search, change searchbox placeholder * Add email-validator to package.json to merge with updated site * Add source plugin to pull in npm package info, add metadata to cards and package detail page * Remove results display when no results * Remove multiple div * Remove startes and filters from packages description * Update searchbar styles * Remove searchbar scroll * Update packages.js * Empty commit * Empty commit * Add plugins.js and searchbar-body.js for searching and displaying gatsby plugins * Remove unneccesary css * Removed package-lock.json and renamed plugins.js to packages.js * Add algolia-npm search and url syncing * Add background color when plugin selected * Fix doubling-up layout bug, add border to hits component, add margin to text in packages * Remove unnecessary dependencies from package.json * Remove withUrlSync.js * Change Algolia link from Link to a tag * Add gatsby-component as keyword search, change searchbox placeholder * Add email-validator to package.json to merge with updated site * Add source plugin to pull in npm package info, add metadata to cards and package detail page * Remove results display when no results * Remove multiple div * Remove startes and filters from packages description * Add plugins.js and searchbar-body.js for searching and displaying gatsby plugins * Remove unneccesary css * Removed package-lock.json and renamed plugins.js to packages.js * Add algolia-npm search and url syncing * Add background color when plugin selected * Fix doubling-up layout bug, add border to hits component, add margin to text in packages * Remove unnecessary dependencies from package.json * Remove withUrlSync.js * Change Algolia link from Link to a tag * Add email-validator to package.json to merge with updated site * Add source plugin to pull in npm package info, add metadata to cards and package detail page * Remove results display when no results * Remove multiple div * Remove startes and filters from packages description * Update searchbar styles * Remove searchbar scroll * Update packages.js * Empty commit * Update template-docs to account for both local and remote packages * Remove duplicate code * Remove commented out code * linting fixes to run tests * removed package-lock * minor fixes to html head, package.json description, TODO notes * minor fixes across files in prep for merge react-icons instead of svgs, updated gitignores for gatsby-node files removed obsolete gatsby-source-npm that was refactored and renamed gatsby-source-npm-package-search shortened css file * removed unused icons * removed unused gatsby-browser.js, used createNodeId on readmes * conditional rendering for packages that aren't found, UI tweaks to search bar on wide screens * plugin library mobile layout * 2nd implementation of mobile ui * Fix getting access to createNodeId createNodeId is a utility library that's passed in and not an NPM package * css deletions overhaul * separate components for template doc packages * using package readme component on template doc packages * added missing dependencies (date-fns and react-instant-search) to package.json * keeping undefined objects from being accessed with default values, conditional rendering of specific metadata not pulled by every package * fix loadNodeContent error, remove old comments * added infinite scroll for plugins * highlighting results list with pagination fix * refactor create page logic to make sure all packages have pages created, and added PropTypes and not found data so undefined errors don't break package readme template components
This was referenced Aug 18, 2021
This was referenced Sep 12, 2021
mwfrost
pushed a commit
to mwfrost/gatsby
that referenced
this pull request
Apr 20, 2023
* Revert "Update gatsby-browser.js (gatsbyjs#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (gatsbyjs#3717) * Publish - gatsby-plugin-no-sourcemaps@1.0.0 * 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 - gatsby-plugin-netlify@1.0.16 - gatsby-plugin-no-sourcemaps@1.0.1 - gatsby-transformer-remark@1.7.30 - gatsby@1.9.170 * 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 - gatsby-link@1.6.35 - gatsby@1.9.171 * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (gatsbyjs#3735) * Publish - gatsby-cli@1.1.32 - gatsby@1.9.172 * 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 - gatsby-plugin-no-sourcemaps@1.0.2 - gatsby-plugin-typography@1.7.13 - gatsby-source-drupal@2.0.17 - gatsby-source-filesystem@1.5.16 - gatsby-source-wordpress@2.0.52 - gatsby@1.9.173 * [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 - gatsby-cli@1.1.33 - gatsby-plugin-netlify@1.0.17 - gatsby@1.9.174 * 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 - gatsby-plugin-google-analytics@1.0.17 - gatsby-plugin-twitter@1.0.16 - gatsby-react-router-scroll@1.0.9 - gatsby@1.9.175 * [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 - gatsby-cli@1.1.34 - gatsby-link@1.6.36 - gatsby-source-contentful@1.3.35 - gatsby@1.9.176 * 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 - gatsby-plugin-less@1.1.1 - gatsby-source-contentful@1.3.36 - gatsby@1.9.177 * 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 - gatsby-plugin-less@1.1.2 - gatsby@1.9.178 * 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 - gatsby-plugin-less@1.1.3 - gatsby-react-router-scroll@1.0.10 - gatsby-remark-copy-linked-files@1.5.26 - gatsby-source-drupal@2.0.18 - gatsby-source-filesystem@1.5.17 - gatsby-source-wordpress@2.0.53 - gatsby@1.9.179 * 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 - gatsby-image@1.0.35 - gatsby-plugin-less@1.1.4 - gatsby-plugin-sitemap@1.2.12 - gatsby-source-contentful@1.3.37 - gatsby-source-drupal@2.0.19 - gatsby-source-filesystem@1.5.18 - gatsby-source-wordpress@2.0.54 - gatsby-transformer-sharp@1.6.18 - gatsby@1.9.180 * 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 - gatsby-cli@1.1.35 - gatsby-transformer-screenshot@1.0.1 - gatsby@1.9.181 * [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 - gatsby-cli@1.1.36 - gatsby-plugin-feed@1.3.17 - gatsby@1.9.182 * use simple https to clone starters (gatsbyjs#3875) * Publish - gatsby-cli@1.1.37 - gatsby@1.9.183 * [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 - gatsby-plugin-netlify-cms@1.0.6 - gatsby-remark-images@1.5.42 - gatsby@1.9.184 * Fix typo (gatsbyjs#3899) * update prismjs-language-dependencies.js (gatsbyjs#3898) * Publish - gatsby-remark-embed-snippet@1.0.7 - gatsby-remark-prismjs@1.2.13 * 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 - gatsby-remark-embed-snippet@1.0.8 - gatsby-remark-images@1.5.43 - gatsby-remark-prismjs@1.2.14 - gatsby-transformer-remark@1.7.31 * 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 - gatsby@1.9.185 * 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 <vlad@vladpasculescu.com> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - gatsby-cli@1.1.38 - gatsby@1.9.186 * 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 - gatsby@1.9.187 * Return a never to be resolved promise to prevent development server from exiting early fixes gatsbyjs#3932 (gatsbyjs#3933) * Publish - gatsby-cli@1.1.39 - gatsby@1.9.188 * 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 - gatsby@1.9.189 * 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 - gatsby@1.9.190 * Add LaserTime Clinic website to Readme (gatsbyjs#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (gatsbyjs#3952) * Publish - gatsby@1.9.191 * 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 - gatsby@1.9.192 * 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 - gatsby-plugin-google-analytics@1.0.18 - gatsby@1.9.193 * 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 - gatsby-1-config-css-modules@1.0.9 - gatsby-cli@1.1.40 - gatsby-dev-cli@1.2.11 - gatsby-image@1.0.36 - gatsby-link@1.6.37 - gatsby-module-loader@1.0.10 - gatsby-plugin-aphrodite@1.0.7 - gatsby-plugin-canonical-urls@1.0.13 - gatsby-plugin-catch-links@1.0.16 - gatsby-plugin-coffeescript@1.4.10 - gatsby-plugin-create-client-paths@1.0.5 - gatsby-plugin-cxs@1.0.7 - gatsby-plugin-emotion@1.1.12 - gatsby-plugin-feed@1.3.18 - gatsby-plugin-glamor@1.6.12 - gatsby-plugin-glamorous@1.0.7 - gatsby-plugin-google-analytics@1.0.19 - gatsby-plugin-google-tagmanager@1.0.14 - gatsby-plugin-jss@1.5.11 - gatsby-plugin-less@1.1.5 - gatsby-plugin-lodash@1.0.9 - gatsby-plugin-manifest@1.0.14 - gatsby-plugin-netlify-cms@1.0.7 - gatsby-plugin-netlify@1.0.18 - gatsby-plugin-no-sourcemaps@1.0.3 - gatsby-plugin-nprogress@1.0.12 - gatsby-plugin-offline@1.0.14 - gatsby-plugin-postcss-sass@1.0.17 - gatsby-plugin-preact@1.0.16 - gatsby-plugin-react-css-modules@1.0.13 - gatsby-plugin-react-helmet@2.0.5 - gatsby-plugin-react-next@1.0.9 - gatsby-plugin-remove-trailing-slashes@1.0.5 - gatsby-plugin-sass@1.0.17 - gatsby-plugin-sharp@1.6.28 - gatsby-plugin-sitemap@1.2.13 - gatsby-plugin-styled-components@2.0.6 - gatsby-plugin-styled-jsx@2.0.3 - gatsby-plugin-styletron@1.0.12 - gatsby-plugin-stylus@1.1.15 - gatsby-plugin-twitter@1.0.17 - gatsby-plugin-typescript@1.4.16 - gatsby-plugin-typography@1.7.14 - gatsby-react-router-scroll@1.0.11 - gatsby-remark-autolink-headers@1.4.12 - gatsby-remark-code-repls@1.0.9 - gatsby-remark-copy-linked-files@1.5.27 - gatsby-remark-custom-blocks@1.0.3 - gatsby-remark-embed-snippet@1.0.9 - gatsby-remark-images@1.5.44 - gatsby-remark-katex@1.0.11 - gatsby-remark-prismjs@1.2.15 - gatsby-remark-responsive-iframe@1.4.17 - gatsby-remark-smartypants@1.4.11 - gatsby-source-contentful@1.3.38 - gatsby-source-drupal@2.0.20 - gatsby-source-faker@1.0.2 - gatsby-source-filesystem@1.5.19 - gatsby-source-hacker-news@1.0.10 - gatsby-source-lever@1.0.8 - gatsby-source-medium@1.0.12 - gatsby-source-mongodb@1.5.14 - gatsby-source-wordpress-com@1.0.6 - gatsby-source-wordpress@2.0.55 - gatsby-transformer-csv@1.3.8 - gatsby-transformer-documentationjs@1.4.9 - gatsby-transformer-docx@1.0.6 - gatsby-transformer-excel@1.0.4 - gatsby-transformer-hjson@1.0.3 - gatsby-transformer-javascript-static-exports@1.3.9 - gatsby-transformer-json@1.0.15 - gatsby-transformer-pdf@1.0.6 - gatsby-transformer-pdfimages@1.0.5 - gatsby-transformer-react-docgen@1.0.13 - gatsby-transformer-remark@1.7.32 - gatsby-transformer-screenshot@1.0.2 - gatsby-transformer-sharp@1.6.19 - gatsby-transformer-toml@1.1.8 - gatsby-transformer-xml@1.0.12 - gatsby-transformer-yaml@1.5.15 - gatsby@1.9.194 - graphql-skip-limit@1.0.10 * [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 - gatsby-remark-katex@1.0.12 - gatsby-transformer-react-docgen@1.0.14 - gatsby@1.9.195 * 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 - gatsby-image@1.0.37 - gatsby@1.9.196 * 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 - gatsby@1.9.197 * 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 - gatsby-source-mongodb@1.5.15 - gatsby-source-wordpress@2.0.56 - gatsby-transformer-javascript-frontmatter@1.0.1 - gatsby-transformer-javascript-static-exports@1.3.10 - gatsby@1.9.198 * 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 - gatsby@1.9.199 * 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
mwfrost
pushed a commit
to mwfrost/gatsby
that referenced
this pull request
Apr 20, 2023
* Revert "Update gatsby-browser.js (gatsbyjs#3694)" This reverts commit 644d081. * Add 'page.layout' param to 'createPage' docs (gatsbyjs#3717) * Publish - gatsby-plugin-no-sourcemaps@1.0.0 * 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 - gatsby-plugin-netlify@1.0.16 - gatsby-plugin-no-sourcemaps@1.0.1 - gatsby-transformer-remark@1.7.30 - gatsby@1.9.170 * 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 - gatsby-link@1.6.35 - gatsby@1.9.171 * If someone uses a private repo git address accessed over ssh use that otherwise use normal git address (gatsbyjs#3735) * Publish - gatsby-cli@1.1.32 - gatsby@1.9.172 * 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 - gatsby-plugin-no-sourcemaps@1.0.2 - gatsby-plugin-typography@1.7.13 - gatsby-source-drupal@2.0.17 - gatsby-source-filesystem@1.5.16 - gatsby-source-wordpress@2.0.52 - gatsby@1.9.173 * [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 - gatsby-cli@1.1.33 - gatsby-plugin-netlify@1.0.17 - gatsby@1.9.174 * 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 - gatsby-plugin-google-analytics@1.0.17 - gatsby-plugin-twitter@1.0.16 - gatsby-react-router-scroll@1.0.9 - gatsby@1.9.175 * [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 - gatsby-cli@1.1.34 - gatsby-link@1.6.36 - gatsby-source-contentful@1.3.35 - gatsby@1.9.176 * 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 - gatsby-plugin-less@1.1.1 - gatsby-source-contentful@1.3.36 - gatsby@1.9.177 * 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 - gatsby-plugin-less@1.1.2 - gatsby@1.9.178 * 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 - gatsby-plugin-less@1.1.3 - gatsby-react-router-scroll@1.0.10 - gatsby-remark-copy-linked-files@1.5.26 - gatsby-source-drupal@2.0.18 - gatsby-source-filesystem@1.5.17 - gatsby-source-wordpress@2.0.53 - gatsby@1.9.179 * 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 - gatsby-image@1.0.35 - gatsby-plugin-less@1.1.4 - gatsby-plugin-sitemap@1.2.12 - gatsby-source-contentful@1.3.37 - gatsby-source-drupal@2.0.19 - gatsby-source-filesystem@1.5.18 - gatsby-source-wordpress@2.0.54 - gatsby-transformer-sharp@1.6.18 - gatsby@1.9.180 * 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 - gatsby-cli@1.1.35 - gatsby-transformer-screenshot@1.0.1 - gatsby@1.9.181 * [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 - gatsby-cli@1.1.36 - gatsby-plugin-feed@1.3.17 - gatsby@1.9.182 * use simple https to clone starters (gatsbyjs#3875) * Publish - gatsby-cli@1.1.37 - gatsby@1.9.183 * [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 - gatsby-plugin-netlify-cms@1.0.6 - gatsby-remark-images@1.5.42 - gatsby@1.9.184 * Fix typo (gatsbyjs#3899) * update prismjs-language-dependencies.js (gatsbyjs#3898) * Publish - gatsby-remark-embed-snippet@1.0.7 - gatsby-remark-prismjs@1.2.13 * 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 - gatsby-remark-embed-snippet@1.0.8 - gatsby-remark-images@1.5.43 - gatsby-remark-prismjs@1.2.14 - gatsby-transformer-remark@1.7.31 * 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 - gatsby@1.9.185 * 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 <vlad@vladpasculescu.com> * Updated Blog Post for Edits Edited Jam Out Blog Post for suggested moderator edits. * Update index.md * Publish - gatsby-cli@1.1.38 - gatsby@1.9.186 * 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 - gatsby@1.9.187 * Return a never to be resolved promise to prevent development server from exiting early fixes gatsbyjs#3932 (gatsbyjs#3933) * Publish - gatsby-cli@1.1.39 - gatsby@1.9.188 * 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 - gatsby@1.9.189 * 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 - gatsby@1.9.190 * Add LaserTime Clinic website to Readme (gatsbyjs#3951) * webpack commonsChunkPlugin isframework tester fix for windows dev (gatsbyjs#3952) * Publish - gatsby@1.9.191 * 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 - gatsby@1.9.192 * 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 - gatsby-plugin-google-analytics@1.0.18 - gatsby@1.9.193 * 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 - gatsby-1-config-css-modules@1.0.9 - gatsby-cli@1.1.40 - gatsby-dev-cli@1.2.11 - gatsby-image@1.0.36 - gatsby-link@1.6.37 - gatsby-module-loader@1.0.10 - gatsby-plugin-aphrodite@1.0.7 - gatsby-plugin-canonical-urls@1.0.13 - gatsby-plugin-catch-links@1.0.16 - gatsby-plugin-coffeescript@1.4.10 - gatsby-plugin-create-client-paths@1.0.5 - gatsby-plugin-cxs@1.0.7 - gatsby-plugin-emotion@1.1.12 - gatsby-plugin-feed@1.3.18 - gatsby-plugin-glamor@1.6.12 - gatsby-plugin-glamorous@1.0.7 - gatsby-plugin-google-analytics@1.0.19 - gatsby-plugin-google-tagmanager@1.0.14 - gatsby-plugin-jss@1.5.11 - gatsby-plugin-less@1.1.5 - gatsby-plugin-lodash@1.0.9 - gatsby-plugin-manifest@1.0.14 - gatsby-plugin-netlify-cms@1.0.7 - gatsby-plugin-netlify@1.0.18 - gatsby-plugin-no-sourcemaps@1.0.3 - gatsby-plugin-nprogress@1.0.12 - gatsby-plugin-offline@1.0.14 - gatsby-plugin-postcss-sass@1.0.17 - gatsby-plugin-preact@1.0.16 - gatsby-plugin-react-css-modules@1.0.13 - gatsby-plugin-react-helmet@2.0.5 - gatsby-plugin-react-next@1.0.9 - gatsby-plugin-remove-trailing-slashes@1.0.5 - gatsby-plugin-sass@1.0.17 - gatsby-plugin-sharp@1.6.28 - gatsby-plugin-sitemap@1.2.13 - gatsby-plugin-styled-components@2.0.6 - gatsby-plugin-styled-jsx@2.0.3 - gatsby-plugin-styletron@1.0.12 - gatsby-plugin-stylus@1.1.15 - gatsby-plugin-twitter@1.0.17 - gatsby-plugin-typescript@1.4.16 - gatsby-plugin-typography@1.7.14 - gatsby-react-router-scroll@1.0.11 - gatsby-remark-autolink-headers@1.4.12 - gatsby-remark-code-repls@1.0.9 - gatsby-remark-copy-linked-files@1.5.27 - gatsby-remark-custom-blocks@1.0.3 - gatsby-remark-embed-snippet@1.0.9 - gatsby-remark-images@1.5.44 - gatsby-remark-katex@1.0.11 - gatsby-remark-prismjs@1.2.15 - gatsby-remark-responsive-iframe@1.4.17 - gatsby-remark-smartypants@1.4.11 - gatsby-source-contentful@1.3.38 - gatsby-source-drupal@2.0.20 - gatsby-source-faker@1.0.2 - gatsby-source-filesystem@1.5.19 - gatsby-source-hacker-news@1.0.10 - gatsby-source-lever@1.0.8 - gatsby-source-medium@1.0.12 - gatsby-source-mongodb@1.5.14 - gatsby-source-wordpress-com@1.0.6 - gatsby-source-wordpress@2.0.55 - gatsby-transformer-csv@1.3.8 - gatsby-transformer-documentationjs@1.4.9 - gatsby-transformer-docx@1.0.6 - gatsby-transformer-excel@1.0.4 - gatsby-transformer-hjson@1.0.3 - gatsby-transformer-javascript-static-exports@1.3.9 - gatsby-transformer-json@1.0.15 - gatsby-transformer-pdf@1.0.6 - gatsby-transformer-pdfimages@1.0.5 - gatsby-transformer-react-docgen@1.0.13 - gatsby-transformer-remark@1.7.32 - gatsby-transformer-screenshot@1.0.2 - gatsby-transformer-sharp@1.6.19 - gatsby-transformer-toml@1.1.8 - gatsby-transformer-xml@1.0.12 - gatsby-transformer-yaml@1.5.15 - gatsby@1.9.194 - graphql-skip-limit@1.0.10 * [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 - gatsby-remark-katex@1.0.12 - gatsby-transformer-react-docgen@1.0.14 - gatsby@1.9.195 * 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 - gatsby-image@1.0.37 - gatsby@1.9.196 * 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 - gatsby@1.9.197 * 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 - gatsby-source-mongodb@1.5.15 - gatsby-source-wordpress@2.0.56 - gatsby-transformer-javascript-frontmatter@1.0.1 - gatsby-transformer-javascript-static-exports@1.3.10 - gatsby@1.9.198 * 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 - gatsby@1.9.199 * 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 - gatsby-plugin-styled-components@2.0.7 - gatsby@1.9.200 * 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 - gatsby-plugin-sharp@1.6.29 - gatsby-remark-images@1.5.45 - gatsby-source-drupal@2.0.21 - gatsby-source-filesystem@1.5.20 - gatsby-source-wordpress@2.0.57 - gatsby@1.9.201 * [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 - gatsby-plugin-sharp@1.6.30 - gatsby-remark-images@1.5.46 * 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 - gatsby@1.9.202
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #3600
@alvinthen so the test proved too simplistic :-) I ran this against the using-wordpress example and it caused an infinite loop as the code added a new linked node as the value which the inferring would recurse into and would find new links returning to the original source :-)