profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/LekoArts/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Lennart LekoArts @gatsbyjs Germany https://www.lekoarts.de He/Him • I’m passionate about working on open source products & building thriving communities around them. • Building themes.lekoarts.de

gatsbyjs/gatsby-starter-shopify 150

A Gatsby starter using the latest Shopify plugin showcasing a store with product overview, individual product pages, and a cart

LekoArts/figma-theme-ui 138

Convert a Theme UI config to Figma Styles

gatsbyjs/themes 111

This is a repo for Gatsby's official themes.

LekoArts/gatsby-from-scratch 14

Gatsby - Step by Step. See the commit history

LekoArts/gatsby 2

⚛️📄🚀 Blazing fast static site generator for React

LekoArts/gatsby-absolute-image-paths 2

Explanation of using absolute image paths in Gatsby in other data sources like JSON

LekoArts/gatsby-example-graphql2chartjs 2

Gatsby + graphql2chartjs

LekoArts/chakra-ui-advanced-multi-part-components 1

Example project showing how to create advanced multi-part components in Chakra UI

LekoArts/dotfiles 1

Configuration files

push eventgatsbyjs/gatsby

LekoArts

commit sha 037fbed92740ffb06047bb8ca25249cad75c69e9

fix consecutive builds failure

view details

push time in 11 hours

delete branch gatsbyjs/gatsby

delete branch : renovate/starters-examples-gatsby-minor

delete time in 13 hours

PR merged gatsbyjs/gatsby

fix(deps): update starters and examples - gatsby topic: automation

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gatsby (changelog) ^3.10.2 -> ^3.11.0 age adoption passing confidence
gatsby-plugin-feed ^3.10.0 -> ^3.11.0 age adoption passing confidence
gatsby-plugin-gatsby-cloud ^2.10.1 -> ^2.11.0 age adoption passing confidence
gatsby-plugin-google-analytics ^3.10.0 -> ^3.11.0 age adoption passing confidence
gatsby-plugin-image ^1.10.1 -> ^1.11.0 age adoption passing confidence
gatsby-plugin-manifest ^3.10.0 -> ^3.11.0 age adoption passing confidence
gatsby-plugin-offline ^4.10.0 -> ^4.11.0 age adoption passing confidence
gatsby-plugin-react-helmet ^4.10.0 -> ^4.11.0 age adoption passing confidence
gatsby-plugin-sharp ^3.10.2 -> ^3.11.0 age adoption passing confidence
gatsby-remark-copy-linked-files ^4.7.0 -> ^4.8.0 age adoption passing confidence
gatsby-remark-images ^5.7.0 -> ^5.8.0 age adoption passing confidence
gatsby-remark-prismjs ^5.7.0 -> ^5.8.0 age adoption passing confidence
gatsby-remark-responsive-iframe ^4.7.0 -> ^4.8.0 age adoption passing confidence
gatsby-remark-smartypants ^4.7.0 -> ^4.8.0 age adoption passing confidence
gatsby-source-filesystem ^3.10.0 -> ^3.11.0 age adoption passing confidence
gatsby-transformer-remark ^4.7.0 -> ^4.8.0 age adoption passing confidence
gatsby-transformer-sharp ^3.10.0 -> ^3.11.0 age adoption passing confidence

Release Notes

<details> <summary>gatsbyjs/gatsby</summary>

v3.11.0

Compare Source

Note: Version bump only for package gatsby-remark-prismjs

</details>


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+4457 -4285

0 comment

16 changed files

renovate[bot]

pr closed time in 13 hours

PullRequestReviewEvent

push eventgatsbyjs/gatsby

LekoArts

commit sha eadfea0f7f5a63a182aa84e5512f03a5e2c4fce1

some cleanup

view details

push time in 15 hours

push eventgatsbyjs/gatsby

LekoArts

commit sha cac5d8862977642362b659ff52409af4dfb8315e

don't hardcode .cache but use __dirname to read sqContext

view details

push time in 16 hours

PR merged gatsbyjs/gatsby

chore(starters): Typo on tsconfig topic: DX

Description

Small typo fix on /using-typescript page in gatsby starter templates. TypeScript tsconfig.json file does not have a dot infront of it.

Documentation

n/a

Related Issues

n/a

+2 -2

0 comment

2 changed files

gabts

pr closed time in 18 hours

PullRequestReviewEvent

issue commentgatsbyjs/gatsby

Gatsby build failing with Unexpected token error but no other details or stacktrace

Removing caches or node_modules sometimes solves it 🤷

chhpt

comment created time in 18 hours

issue closedgatsbyjs/gatsby

Gatsby build failing with Unexpected token error but no other details or stacktrace

Preliminary Checks

  • [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
  • [X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

It works well in development mode, but build fail and there is no other error details.

failed Building production JavaScript and CSS bundles - 1.742s

 ERROR #98123  WEBPACK

Generating JavaScript bundles failed

Unexpected token (12:287)

File: .cache/production-app.js:12:287

Reproduction Link

https://github.com/chhpt/gatsby-ts-starter

Steps to Reproduce

  1. install dependencies: yarn
  2. yarn run build

Expected Result

Build success

Actual Result

Build fail

Environment

macOS 11.5, node 14.16.0, npm 6.14.11

Config Flags

No

closed time in 18 hours

chhpt

issue commentgatsbyjs/gatsby

Gatsby build failing with Unexpected token error but no other details or stacktrace

Then you shouldn't have the issue anymore. I've used yarn resolutions to force the version to 7.15.0 and I see the error. After forcing to 7.15.1 the error goes away 👍


So if you see the error please update your packages and check that you have @babel/plugin-transform-react-display-name@7.15.1 installed or anything below 7.15.0

chhpt

comment created time in 18 hours

issue commentgatsbyjs/gatsby

Gatsby build failing with Unexpected token error but no other details or stacktrace

Can you run yarn why @babel/plugin-transform-react-display-name in your repo @chenxizhang ?

As others pointed out it might have been caused by https://github.com/babel/babel/pull/13501 which was just reverted in https://github.com/babel/babel/pull/13637 and released in https://github.com/babel/babel/commit/546e3d958d337cd1fb59f8242d46fd062b7f2a45#diff-01ecfc1ff84980d33a414eec403fcb86a6c9f61979ac6163753744719b8110ed (7.15.1)

chhpt

comment created time in 19 hours

issue commentgatsbyjs/gatsby

Gatsby build failing with Unexpected token error but no other details or stacktrace

Hi!

I've cloned the starter https://github.com/chhpt/gatsby-ts-starter, removed the yarn.lock file, run yarn and then yarn build and I don't see any issues:

image

Can you please provide a reproduction showing this issue, including the steps necessary?

chhpt

comment created time in 19 hours

issue closedgatsbyjs/gatsby

Refresh page on production going back to / page

Preliminary Checks

  • [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
  • [X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Currently I deploy the project on aws-amplify. if I navigate using gatsby navigate it's working fine. but after I refresh the page, it will redirect the page to / . Currently I use gatsby v3.

I setup the rewrite rules

</^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|woff2|ttf|map|json)$)([^.]+$)/> to /index.html

Reproduction Link

0

Steps to Reproduce

  1. Go to some page like /signup
  2. refresh the page will go to / ...

Expected Result

Should stay on the page

Actual Result

go to / page

Environment

gatsby v3

Config Flags

No response

closed time in 20 hours

adrianhp97

issue closedgatsbyjs/gatsby

Gatsby 3.11.0 - Generating JavaScript bundles failed

Preliminary Checks

  • [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
  • [X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Getting errors after updating Gatsby from 3.10.2 to 3.11.0.

ERROR #98123  WEBPACK

Generating JavaScript bundles failed

Unexpected token (12:287)

File: .cache/production-app.js:12:287

Reproduction Link

0

Steps to Reproduce

  1. Update gatsby-cli
  2. Update Gatsby from 3.10.2 to 3.11.0
  3. gatsby clean && gatsby build ...

Expected Result

The site should build as per normal

Actual Result

Getting error as below

ERROR #98123  WEBPACK

Generating JavaScript bundles failed

Unexpected token (12:287)

File: .cache/production-app.js:12:287

Environment

System:
    OS: macOS 11.5.1
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 92.0.4515.131
    Safari: 14.1.2
  npmPackages:
    gatsby: ^3.11.0 => 3.11.0 
    gatsby-plugin-catch-links: ^3.11.0 => 3.11.0 
    gatsby-plugin-google-analytics: ^3.11.0 => 3.11.0 
    gatsby-plugin-image: ^1.11.0 => 1.11.0 
    gatsby-plugin-manifest: ^3.11.0 => 3.11.0 
    gatsby-plugin-mdx: ^2.11.0 => 2.11.0 
    gatsby-plugin-netlify: ^3.11.0 => 3.11.0 
    gatsby-plugin-preact: ^5.11.0 => 5.11.0 
    gatsby-plugin-react-helmet: ^4.11.0 => 4.11.0 
    gatsby-plugin-remove-serviceworker: ^1.0.0 => 1.0.0 
    gatsby-plugin-robots-txt: ^1.6.8 => 1.6.8 
    gatsby-plugin-sharp: ^3.11.0 => 3.11.0 
    gatsby-plugin-sitemap: ^4.7.0 => 4.7.0 
    gatsby-plugin-styled-components: ^4.11.0 => 4.11.0 
    gatsby-remark-autolink-headers: ^4.8.0 => 4.8.0 
    gatsby-remark-images: ^5.8.0 => 5.8.0 
    gatsby-remark-unwrap-images: ^1.0.2 => 1.0.2 
    gatsby-source-filesystem: ^3.11.0 => 3.11.0 
    gatsby-transformer-sharp: ^3.11.0 => 3.11.0 
  npmGlobalPackages:
    gatsby-cli: 3.11.0


### Config Flags

_No response_

closed time in 20 hours

flikteoh

issue commentgatsbyjs/gatsby

Gatsby 3.11.0 - Generating JavaScript bundles failed

I'm closing this in favor of https://github.com/gatsbyjs/gatsby/issues/32705 because you didn't provide a reproduction.

flikteoh

comment created time in 20 hours

push eventgatsbyjs/gatsby

LekoArts

commit sha 8299db7d0b6e4428e66fb6543f7ab720c2092f8f

wip static queries

view details

push time in a day

delete branch gatsbyjs/gatsby

delete branch : feat/de183d-sq

delete time in a day

create barnchgatsbyjs/gatsby

branch : feat/de183d-sq

created branch time in a day

push eventgatsbyjs/gatsby

LekoArts

commit sha c7cdfaa53e6a6c0808c8f0fe380109818d96d7db

add cache: true to cache-lmdb

view details

push time in 2 days

PR merged gatsbyjs/gatsby

fix(gatsby-plugin-sitemap): Add plugin options forbidden for deprecated `exclude` topic: plugins

In gatsby-plugin-sitemap 3 - > 4 exclude turned into excludes but the error message looked like:

Error: Body must be a string. Received: undefined.

For the old config. Given that most people would probably upgrade like I did via "Gatsby 2->3" and all libraries with it, I read the migration for Gatsby but not each official plugin.

I resisted the temptation to randomly duckduckgo for the error message on this one for a while, but the message was a red herring. Eventually I gave up and found https://github.com/gatsbyjs/gatsby/issues/31416#issuecomment-841301948 - so this should give a better error message for folks migrating.

+15 -0

1 comment

2 changed files

orta

pr closed time in 2 days

push eventgatsbyjs/gatsby

Lennart

commit sha 10be4afdc46a9fc3458fa6f5a937e8be63b66d83

Update index.md

view details

push time in 2 days

push eventgatsbyjs/gatsby

Lennart

commit sha 42eb8122cfaca625c84ce91d11e854450b5f7f46

Update index.md

view details

push time in 2 days

push eventgatsbyjs/gatsby

Lennart

commit sha a235e3992d83f5bce1c4c6bc82ced713ca3f3011

correct base-head for git compare links

view details

push time in 2 days

PullRequestReviewEvent

pull request commentgatsbyjs/gatsby

Adds support for better error messaging when updating gatsby-plugin-sitemap

Thanks for the PR!

I've changed it to use our Plugin Options API: https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/configuring-usage-with-plugin-options/

We've got a section on deprecating options there (sadly it wasn't done in the initial PR): https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/configuring-usage-with-plugin-options/#deprecating-options

It'll then also immediately fail:

ERROR #11331  PLUGIN

Invalid plugin options for "gatsby-plugin-sitemap":

- As of v4 the `exclude` option was renamed to `excludes`

not finished open and validate gatsby-configs, load plugins - 0.256s

error Command failed with exit code 1.
orta

comment created time in 2 days

push eventorta/gatsby

LekoArts

commit sha 983b701cb4a4eccd203ba3b4b9cdd9635183b3ac

revert previous changes

view details

LekoArts

commit sha 93c90d602dd4f4a34bb9467e43baec90f4c3bf5a

add plugin options forbidden

view details

push time in 2 days

push eventgatsbyjs/gatsby

LekoArts

commit sha 95191a2c5cb2f9875efb281152b323cc408b9f64

update lock file

view details

push time in 2 days

push eventgatsbyjs/gatsby

Sayanta Banerjee

commit sha f7ce2991878fb92ae89c693e7aad6a27d537f954

chore(starters): Update links in README-template (#32549) Co-authored-by: Lennart <lekoarts@gmail.com>

view details

push time in 2 days

PR merged gatsbyjs/gatsby

chore(starters): Update links in README-template type: documentation
  • Fixed sentence clarity and grammatical errors
  • Updated the links

<!-- Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or ask in this Pull Request and a Gatsby maintainer will be happy to help :) -->

<!-- Is this a blog post? Check out the docs at https://www.gatsbyjs.com/contributing/blog-contributions/, and please mention if the blog post is pre-approved by someone from Gatsby. -->

Description

<!-- Write a brief description of the changes introduced by this PR -->

Documentation

<!-- Where is this feature or API documented?

  • If docs exist:
    • Update any references, if relevant. This includes Guides and Gatsby Internals docs.
  • If no docs exist:
    • Create a stub for documentation including bullet points for how to use the feature, code snippets (including from happy path tests), etc.
  • Tag @gatsbyjs/documentation for review, pairing, polishing of the documentation -->

Related Issues

<!-- Link to the issue that is fixed by this PR (if there is one) e.g. Fixes #1234

Link to an issue that is partially addressed by this PR (if there are any) e.g. Addresses #1234

Link to related issues (if there are any) e.g. Related to #1234 -->

+5 -5

1 comment

1 changed file

Sayanta66

pr closed time in 2 days