You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/gatsby-plugin-image/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -316,11 +316,11 @@ The optional helper function `getImage` takes a file node and returns `file?.chi
316
316
317
317
These arguments can be passed to the `gatsbyImageData()` resolver:
318
318
319
-
-**width**: The display width of the generated image. The actual largest image resolution will be this value multipled by the largest value in outputPixelDensities. Ignored if layout = FLUID or CONSTRAINED, where you should use "maxWidth" instead.
319
+
-**width**: The display width of the generated image. The actual largest image resolution will be this value multiplied by the largest value in outputPixelDensities. Ignored if layout = FLUID or CONSTRAINED, where you should use "maxWidth" instead.
320
320
-**height**: If set, the height of the generated image. If omitted, it is calculated from the supplied width, matching the aspect ratio of the source image.
321
321
-**maxWidth**:
322
322
Maximum display width of generated files.
323
-
The actual largest image resolution will be this value multipled by the largest value in outputPixelDensities
323
+
The actual largest image resolution will be this value multiplied by the largest value in outputPixelDensities
324
324
This only applies when layout = FLUID or CONSTRAINED. For other layout types, use "width"
325
325
-**maxHeight**: If set, the generated image is a maximum of this height, cropping if necessary. If the image layout is "constrained" then the image will be limited to this height. If the aspect ratio of the image is different than the source, then the image will be cropped.`,
326
326
-**placeholder**: Format of generated placeholder image.
@@ -336,7 +336,7 @@ These arguments can be passed to the `gatsbyImageData()` resolver:
336
336
Default is `[ 0.25, 0.5, 1, 2 ]`, for fluid/constrained images, and `[ 1, 2 ]` for fixed. In this case, an image with a fluid layout and maxWidth = 400 would generate images at 100, 200, 400 and 800px wide
337
337
-**sizes**: The "[sizes](https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images)" attribute, passed to the `<img>` tag. This describes the display size of the image. This does not affect the generated images, but is used by the browser to decide which images to download. You can leave this blank for fixed images, or if the responsive image container will be the full width of the screen. In these cases we will generate an appropriate value. If, however, you are generating responsive images that are not the full width of the screen, you should provide a sizes property for best performance. You can alternatively pass this value to the component.
338
338
-**formats**: an array of file formats to generate. The default is `[AUTO, WEBP]`, which means it will generate images in the same format as the source image, as well as in the next-generation [WebP](https://developers.google.com/speed/webp) format. We strongly recommend you do not change this option, as doing so will affect performance scores.
339
-
-**quality**: The default quality. This is overriden by any format-specific options
339
+
-**quality**: The default quality. This is overridden by any format-specific options
340
340
-**blurredOptions**: Options for the low-resolution placeholder image. Set placeholder to "BLURRED" to use this
Copy file name to clipboardExpand all lines: packages/gatsby-remark-autolink-headers/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ module.exports = {
90
90
91
91
## How to style the anchor link
92
92
93
-
By default, the anchor link has a class of `anchor` (see `className` option to change this name) on the element but has no additional styling. To make it fit your website, you'll have to write some CSS to change the appeareance.
93
+
By default, the anchor link has a class of `anchor` (see `className` option to change this name) on the element but has no additional styling. To make it fit your website, you'll have to write some CSS to change the appearance.
94
94
95
95
In your CSS you can specify this element, in this instance the anchor tag will appear red:
Copy file name to clipboardExpand all lines: packages/gatsby/CHANGELOG.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1161,7 +1161,7 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline
1161
1161
### Bug Fixes
1162
1162
1163
1163
-**gatsby:** don't fail validation on fragments that are not used ([#24032](https://github.com/gatsbyjs/gatsby/issues/24032)) ([61d0ef4](https://github.com/gatsbyjs/gatsby/commit/61d0ef4))
1164
-
-**gatsby:** update script to generate apis.json to accomodate Typescript ([#24023](https://github.com/gatsbyjs/gatsby/issues/24023)) ([7878d0f](https://github.com/gatsbyjs/gatsby/commit/7878d0f))
1164
+
-**gatsby:** update script to generate apis.json to accommodate Typescript ([#24023](https://github.com/gatsbyjs/gatsby/issues/24023)) ([7878d0f](https://github.com/gatsbyjs/gatsby/commit/7878d0f))
Copy file name to clipboardExpand all lines: rfcs/text/000-cli-redesign.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ The user can:
71
71
-[x] select a starter in the CLI without needing a URL. See PR https://github.com/gatsbyjs/gatsby/pull/14097
72
72
-[ ] be redirected to the correct URL when typing in “localhost:8000/\_\_ graphiql incorrectly (we could either redirect to "correct" one or just support multiple different cases)
73
73
-[ ] be directed to another localhost address is localhost:8000 is already taken (https://github.com/gatsbyjs/gatsby/issues/368 and https://github.com/gatsbyjs/gatsby/issues/13512#issuecomment-485781525)
74
-
-[ ] misspell a Gatsby command and the CLI will run the correct command anyway just like Google search does when you mispell something (requires us to update the did-you-mean file). https://github.com/gatsbyjs/gatsby/issues/13512
74
+
-[ ] misspell a Gatsby command and the CLI will run the correct command anyway just like Google search does when you misspell something (requires us to update the did-you-mean file). https://github.com/gatsbyjs/gatsby/issues/13512
75
75
-[ ] get createPages page count in output to help users optimize for speed and catch errors faster''
76
76
-[ ] get notified that they might need to hit `r` if they’ve changed package.json, gatsby node, etc. when `gatsby develop` is running
77
77
-[ ] see only relevant warnings; e.g. omission of peer dependency warnings that they can ignore
Copy file name to clipboardExpand all lines: rfcs/text/0006-node-8-minimum-version.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ We've internally discussed something called `gatsby doctor` which can be run pri
112
112
113
113
This proposal requires documentation to be updated. Our documentation can be considered a code style-guide and oftentimes developers directly copy and paste from our documentation. If we are documenting what we think is a best practice (e.g. Node 6 features like async/await) we are implicitly easing the migration cost of any developer who reads our documentation--which is hopefully all of them!
114
114
115
-
I strongly feel that tweaking the documentation, as well as minimum version requirements, will lead to developers having a _better_ experience using Gatsby, and Gatsby as a whole becomes easier to teach. It resolves the idiosyncracy of _why_ do I need a global install and _when_ do I use `async` / `await` or `return new Promise`. This change should have a net positive impact on the ease-of-use of teaching Gatsby to new and experienced developers, alike.
115
+
I strongly feel that tweaking the documentation, as well as minimum version requirements, will lead to developers having a _better_ experience using Gatsby, and Gatsby as a whole becomes easier to teach. It resolves the idiosyncrasy of _why_ do I need a global install and _when_ do I use `async` / `await` or `return new Promise`. This change should have a net positive impact on the ease-of-use of teaching Gatsby to new and experienced developers, alike.
0 commit comments