@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
3. Updating all Gatsby related packages to latest
4. Removed gatsby-plugin-typescript
5. Removed gatsby-plugin-feed
6. Removed typeface-ibm-plex-sans npm package

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
3. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
4. The TypeScript plugin isn't necessary anymore with Gatsby v3
5. The plugin and its config was moved to the starter. You can copy the configuration from there into your own gatsby-config.js
6. The starter now handles loading the font (via gatsby-omni-font-loader). This enables you to switch the primary font more easily (once you updated the Theme UI config). You can copy the configuration from there into your own gatsby-config.js

Improvements

• Performance improvements from theme-ui upgrade
• Fixed #415

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-minimal-blog) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Move gatsby-plugin-feed from theme to starter
• Use gatsby-omni-font-loader to load the primary font ("IBM Plex Sans") instead of in the theme itself

Patch Changes

• Updated dependencies [1785dcf]:
  • @lekoarts/[email protected]

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
3. Updating all Gatsby related packages to latest
4. Removed gatsby-plugin-typescript
5. Removed gatsby-plugin-feed
6. Removed typeface-ibm-plex-sans npm package

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
3. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
4. The TypeScript plugin isn't necessary anymore with Gatsby v3
5. The plugin and its config was moved to the starter. You can copy the configuration from there into your own gatsby-config.js
6. The starter now handles loading the font (via gatsby-omni-font-loader). This enables you to switch the primary font more easily (once you updated the Theme UI config). You can copy the configuration from there into your own gatsby-config.js

Improvements

• Performance improvements from theme-ui upgrade
• Fixed #415

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-minimal-blog) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Move gatsby-plugin-feed from theme to starter
• Use gatsby-omni-font-loader to load the primary font ("IBM Plex Sans") instead of in the theme itself

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
3. Updating all Gatsby related packages to latest
4. Migrated from gatsby-image to gatsby-plugin-image
5. Removed fontsource-work-sans npm package

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
3. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
4. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
5. The starter now handles loading the font (via gatsby-omni-font-loader). This enables you to switch the primary font more easily (once you updated the Theme UI config). You can copy the configuration from there into your own gatsby-config.js

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from theme-ui upgrade
• Eagerly load the first image in the grid (better lighthouse score)

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-jodie) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Conditionally add gatsby-plugin-webpack-bundle-analyser-v2
• Use gatsby-omni-font-loader to load the primary font ("Work Sans") instead of in the theme itself
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Remove gatsby-source-instagram as Instagram locked down its API (and public scraping methods) even further. The page is now called /art and showcases the custom page in the same way

Patch Changes

• Updated dependencies [1785dcf]:
  • @lekoarts/[email protected]

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
3. Updating all Gatsby related packages to latest
4. Migrated from gatsby-image to gatsby-plugin-image
5. Removed fontsource-work-sans npm package

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
3. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
4. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
5. The starter now handles loading the font (via gatsby-omni-font-loader). This enables you to switch the primary font more easily (once you updated the Theme UI config). You can copy the configuration from there into your own gatsby-config.js

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from theme-ui upgrade
• Eagerly load the first image in the grid (better lighthouse score)

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-jodie) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Conditionally add gatsby-plugin-webpack-bundle-analyser-v2
• Use gatsby-omni-font-loader to load the primary font ("Work Sans") instead of in the theme itself
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Remove gatsby-source-instagram as Instagram locked down its API (and public scraping methods) even further. The page is now called /art and showcases the custom page in the same way

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Removed gatsby-plugin-typescript & gatsby-plugin-emotion

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. The TypeScript plugin isn't necessary anymore with Gatsby v3

Improvements

• Performance improvements from theme-ui upgrade

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-graphql-playground) and didn't change anything else this section will be more relevant to you.

• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating react-spring from v8 to v9
3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
4. Removed @emotion/styled
5. Updating all Gatsby related packages to latest
6. Migrated from gatsby-image to gatsby-plugin-image
7. Removed gatsby-plugin-typescript & gatsby-plugin-emotion

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900
3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
4. If you still want to use @emotion/styled you'll need to install it separately now
5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
6. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
7. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from react-spring and theme-ui upgrades
• Eagerly load the first image in the grid (better lighthouse score)
• Update header/navigation for better mobile view

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-emma) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions

Patch Changes

• Updated dependencies [1785dcf]:
  • @lekoarts/[email protected]

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating react-spring from v8 to v9
3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
4. Removed @emotion/styled
5. Updating all Gatsby related packages to latest
6. Migrated from gatsby-image to gatsby-plugin-image
7. Removed gatsby-plugin-typescript & gatsby-plugin-emotion

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900
3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
4. If you still want to use @emotion/styled you'll need to install it separately now
5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
6. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
7. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from react-spring and theme-ui upgrades
• Eagerly load the first image in the grid (better lighthouse score)
• Update header/navigation for better mobile view

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-emma) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating react-spring from v8 to v9
3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
4. Removed @emotion/styled
5. Updating all Gatsby related packages to latest
6. Migrated from gatsby-image to gatsby-plugin-image
7. Removed gatsby-plugin-typescript & gatsby-plugin-emotion
8. Removed the colorThief node field
9. Normal CSS grid layout (instead of Masonry layout)

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900. The most notable change is the import that was used inside the components. From import { ParallaxLayer } from "react-spring/renderprops-addons.cjs" to import { ParallaxLayer } from "@react-spring/parallax"
3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
4. If you still want to use @emotion/styled you'll need to install it separately now
5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
6. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
7. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself
8. The gatsby-plugin-image now exposes the dominant color via the placeholder itself
9. The Masonry layout was a bit hacky, so I switched it to a normal CSS grid layout. You could shadow the card component to try something on your own. Once the CSS spec itself has a native masonry layout I'll add it back

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from react-spring and theme-ui upgrades
• Eagerly load the first image in the grid (better lighthouse score)

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-emilia) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Add 404 page

Patch Changes

• Updated dependencies [1785dcf]:
  • @lekoarts/[email protected]

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating react-spring from v8 to v9
3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
4. Removed @emotion/styled
5. Updating all Gatsby related packages to latest
6. Migrated from gatsby-image to gatsby-plugin-image
7. Removed gatsby-plugin-typescript & gatsby-plugin-emotion
8. Removed the colorThief node field
9. Normal CSS grid layout (instead of Masonry layout)

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900. The most notable change is the import that was used inside the components. From import { ParallaxLayer } from "react-spring/renderprops-addons.cjs" to import { ParallaxLayer } from "@react-spring/parallax"
3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
4. If you still want to use @emotion/styled you'll need to install it separately now
5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
6. The theme itself is completely migrated to the new image plugin, but if you shadowed components and relied on the old structure, you'll need to migrate to gatsby-plugin-image: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/
7. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself
8. The gatsby-plugin-image now exposes the dominant color via the placeholder itself
9. The Masonry layout was a bit hacky, so I switched it to a normal CSS grid layout. You could shadow the card component to try something on your own. Once the CSS spec itself has a native masonry layout I'll add it back

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from react-spring and theme-ui upgrades
• Eagerly load the first image in the grid (better lighthouse score)

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-emilia) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Add 404 page

@lekoarts/[email protected]

Major Changes

#599 1785dcf Thanks @LekoArts!

Breaking Changes

1. Using lessBabel option for gatsby-plugin-mdx
2. Updating react-spring from v8 to v9
3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
4. Removed @emotion/styled
5. Updating all Gatsby related packages to latest
6. Removed gatsby-plugin-typescript & gatsby-plugin-emotion

Migrating

1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900. The most notable change is the import that was used inside the components. From import { ParallaxLayer } from "react-spring/renderprops-addons.cjs" to import { ParallaxLayer } from "@react-spring/parallax"
3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
4. If you still want to use @emotion/styled you'll need to install it separately now
5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
6. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself

Improvements

• You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
• Performance improvements from react-spring and theme-ui upgrades
• Additional props to the ProjectCard component are now spread by default in the components config of gatsby-plugin-theme-ui

Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-cara) and didn't change anything else this section will be more relevant to you.

• Conditionally add gatsby-plugin-google-analytics
• Add FAST_DEV flag
• Update to all latest Gatsby (+ plugins) versions
• Add 404 page