deployment is successful but the repo is empty. So CMS cannot be used

https://github.com/hansugu/gatsby-homepage

Seeing error when trying to run a freshly downloaded copy of the source:
Error: ObjectMiddleware.register: serializer for mini-css-extract-plugin/dist/CssModule/null is already registered

Steps to repro:

gatsby new gatsby-starter-foundation https://github.com/stackrole/gatsby-starter-foundation
cd gatsby-starter-foundation
gatsby develop

Environment:

Windows 10
gatsby --version:
Gatsby CLI version: 3.4.0
Gatsby version: 3.4.1 Note: this is the Gatsby version for the site at: C:\sourcerepo\gatsby-starter-foundation
npm --version
6.14.8
git --version
git version 2.31.1.windows.1

Troubleshooting Done

deleted node_modules folder
deleted package-lock.json
Cleared caches
gatsby clean
npm cache clear --force
Rebooted the machine
I can run other gatsby starters without issue

Raw Output:

C:\sourcerepo\gatsby-starter-foundation>gatsby develop
info

There are 6 other flags available that you might be interested in:

• FAST_DEV · Enable all experiments aimed at improving develop server start time
• DEV_SSR · (Umbrella Issue (https://gatsby.dev/dev-ssr-feedback)) · Server Side Render (SSR) pages on full reloads during develop. Helps you detect SSR bugs and fix them without needing to do full builds.
• PRESERVE_WEBPACK_CACHE · (Umbrella Issue (https://gatsby.dev/cache-clearing-feedback)) · Use webpack's persistent caching and don't delete webpack's cache when changing gatsby-node.js & gatsby-config.js
  files.
• PRESERVE_FILE_DOWNLOAD_CACHE · (Umbrella Issue (https://gatsby.dev/cache-clearing-feedback)) · Don't delete the downloaded files cache when changing gatsby-node.js & gatsby-config.js files.
• PARALLEL_SOURCING · EXPERIMENTAL · (Umbrella Issue (https://gatsby.dev/parallel-sourcing-feedback)) · Run all source plugins at the same time instead of serially. For sites with multiple source plugins, this
  can speedup sourcing and transforming considerably.
• FUNCTIONS · EXPERIMENTAL · (Umbrella Issue (https://gatsby.dev/functions-feedback)) · Compile Serverless functions in your Gatsby project and write them to disk, ready to deploy to Gatsby Cloud

success open and validate gatsby-configs - 0.307s
success load plugins - 2.750s
success onPreInit - 0.055s
success initialize cache - 0.012s
success copy gatsby files - 0.349s
success onPreBootstrap - 0.045s
success createSchemaCustomization - 0.100s
success Checking for changed pages - 0.003s
success source and transform nodes - 0.703s
success building schema - 1.229s
success createPages - 0.165s
success createPagesStatefully - 0.131s
info Total nodes: 143, SitePage nodes: 19 (use --verbose for breakdown)
success Checking for changed pages - 0.001s
success update schema - 0.138s
success write out redirect data - 0.003s
success Build manifest and related icons - 0.108s
success onPostBootstrap - 0.118s
info bootstrap finished - 10.115s
success onPreExtractQueries - 0.002s
success extract queries from components - 2.341s
success write out requires - 0.108s
success run static queries - 0.064s - 3/3 47.03/s
success run page queries - 3.684s - 3/3 0.81/s

ERROR

ObjectMiddleware.register: serializer for mini-css-extract-plugin/dist/CssModule/null is already registered

Error: ObjectMiddleware.register: serializer for mini-css-extract-plugin/dist/CssModule/null is already registered

• ObjectMiddleware.js:182 Object.register
  [gatsby-starter-foundation]/[webpack]/lib/serialization/ObjectMiddleware.js:182:10

• index.js:163 Function.getCssModule
  [gatsby-starter-foundation]/[mini-css-extract-plugin]/dist/index.js:163:34

• index.js:371 MiniCssExtractPlugin.apply
  [gatsby-starter-foundation]/[mini-css-extract-plugin]/dist/index.js:371:44

• webpack.js:74 createCompiler
  [gatsby-starter-foundation]/[webpack]/lib/webpack.js:74:12

• webpack.js:123 create
  [gatsby-starter-foundation]/[webpack]/lib/webpack.js:123:16

• webpack.js:147 webpack
  [gatsby-starter-foundation]/[webpack]/lib/webpack.js:147:32

• index.js:54 f
  [gatsby-starter-foundation]/[webpack]/lib/index.js:54:15

• start-server.ts:164 startServer
  [gatsby-starter-foundation]/[gatsby]/src/utils/start-server.ts:164:20

• task_queues.js:62 runNextTicks
  internal/process/task_queues.js:62:5

• timers.js:434 processImmediate
  internal/timers.js:434:9

• start-webpack-server.ts:44 startWebpackServer
  [gatsby-starter-foundation]/[gatsby]/src/services/start-webpack-server.ts:44:7

not finished Building development bundle - 7.416s

Hi there,

I'm using the repo as a template for a project that I'm working on.

When building locally, I'm able to view the changes. However, the build fails when pushing to GitHub.

My package.json

{
  "name": "@ashnaz87/afghanistan-turks-association",
  "description": "Repository for Afghanistan Turks Association UK website",
  "version": "1.0.0",
  "author": "AshNaz87 <[email protected]>",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/AshNaz87/afghanistan-turks-association.git"
  },
  "bugs": {
    "url": "https://github.com/AshNaz87/afghanistan-turks-association/issues"
  },
  "scripts": {
    "build": "GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages",
    "develop": "gatsby develop",
    "format": "prettier --write \"**/*.{js,jsx,json,md}\"",
    "start": "npm run develop",
    "serve": "gatsby serve",
    "clean": "gatsby clean",
    "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1"
  },
  "dependencies": {
    "bootstrap-scss": "^4.5.3",
    "gatsby": "^2.27.4",
    "gatsby-background-image": "^1.1.1",
    "gatsby-image": "^2.4.3",
    "gatsby-plugin-advanced-sitemap": "^1.5.4",
    "gatsby-plugin-google-analytics": "^2.3.2",
    "gatsby-plugin-manifest": "^2.4.3",
    "gatsby-plugin-netlify-cms": "^4.3.2",
    "gatsby-plugin-netlify-cms-paths": "^1.3.0",
    "gatsby-plugin-offline": "^3.2.2",
    "gatsby-plugin-react-helmet": "^3.3.1",
    "gatsby-plugin-sass": "^2.3.1",
    "gatsby-plugin-sharp": "^2.9.1",
    "gatsby-remark-images": "^3.3.3",
    "gatsby-remark-prismjs": "^3.5.1",
    "gatsby-remark-reading-time": "^1.1.0",
    "gatsby-remark-responsive-iframe": "^2.4.2",
    "gatsby-source-filesystem": "^2.6.1",
    "gatsby-transformer-remark": "^2.11.1",
    "gatsby-transformer-sharp": "^2.5.2",
    "netlify-cms-app": "^2.14.1",
    "node-sass": "^4.14.1",
    "prismjs": "^1.20.0",
    "react": "^16.12.0",
    "react-dom": "^16.12.0",
    "react-helmet": "^6.0.0",
    "react-icons": "^3.10.0"
  },
  "devDependencies": {
    "acorn": "^6.4.1",
    "netlify-cms-lib-widgets": "^1.3.0",
    "prettier": "2.0.5",
    "react-refresh": "^0.8.2",
    "redux": "^3.0.0",
    "typescript": "^3.9.2"
  }
}

When running gatsby info I get

 System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 6.8.0 - ~/.node_modules_global/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 87.0.4280.67
    Firefox: 83.0
    Safari: 14.0.1
  npmPackages:
    gatsby: ^2.27.4 => 2.27.5 
    gatsby-background-image: ^1.1.1 => 1.3.1 
    gatsby-image: ^2.4.3 => 2.6.0 
    gatsby-plugin-advanced-sitemap: ^1.5.4 => 1.5.6 
    gatsby-plugin-google-analytics: ^2.3.2 => 2.6.0 
    gatsby-plugin-manifest: ^2.4.3 => 2.7.0 
    gatsby-plugin-netlify-cms: ^4.3.2 => 4.5.0 
    gatsby-plugin-netlify-cms-paths: ^1.3.0 => 1.3.0 
    gatsby-plugin-offline: ^3.2.2 => 3.5.0 
    gatsby-plugin-react-helmet: ^3.3.1 => 3.5.0 
    gatsby-plugin-sass: ^2.3.1 => 2.6.0 
    gatsby-plugin-sharp: ^2.9.1 => 2.9.1 
    gatsby-remark-images: ^3.3.3 => 3.6.0 
    gatsby-remark-prismjs: ^3.5.1 => 3.8.0 
    gatsby-remark-reading-time: ^1.1.0 => 1.1.0 
    gatsby-remark-responsive-iframe: ^2.4.2 => 2.6.0 
    gatsby-source-filesystem: ^2.6.1 => 2.6.1 
    gatsby-transformer-remark: ^2.11.1 => 2.11.1 
    gatsby-transformer-sharp: ^2.5.2 => 2.7.0 
  npmGlobalPackages:
    gatsby-cli: 2.14.1

From the deploy logs:

11:37:13 PM: success write out redirect data - 0.001s
11:37:13 PM: vips_value_hash: no case for NULL
11:37:13 PM: 	type 64, gchararray
11:37:13 PM: 	generic 53, GParamString
11:37:13 PM: vips_value_hash: no case for 0.000000
11:37:13 PM: 	type 60, gdouble
11:37:13 PM: 	generic 109, GParamDouble
11:37:13 PM: vips_value_hash: no case for FALSE
11:37:13 PM: 	type 20, gboolean
11:37:13 PM: 	generic 76, GParamBoolean
11:37:13 PM: vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
11:37:13 PM: 	type 71654592, VipsAccess
11:37:13 PM: 	generic 80, GParamEnum
11:37:13 PM: vips_value_hash: no case for FALSE
11:37:13 PM: 	type 20, gboolean
11:37:13 PM: 	generic 76, GParamBoolean
11:37:14 PM: ​
11:37:14 PM: ────────────────────────────────────────────────────────────────
11:37:14 PM:   "build.command" failed                                        
11:37:14 PM: ────────────────────────────────────────────────────────────────
11:37:14 PM: ​
11:37:14 PM:   Error message
11:37:14 PM:   Command was killed with SIGSEGV (Segmentation fault): gatsby build
11:37:14 PM: ​
11:37:14 PM:   Error location
11:37:14 PM:   In build.command from netlify.toml:
11:37:14 PM:   gatsby build
11:37:14 PM: ​
11:37:14 PM:   Resolved config
11:37:14 PM:   build:
11:37:14 PM:     command: gatsby build
11:37:14 PM:     commandOrigin: config
11:37:14 PM:     environment:
11:37:14 PM:       - NODE_VERSION
11:37:14 PM:     publish: /opt/build/repo/public
11:37:14 PM:   plugins:
11:37:14 PM:     - inputs: {}
11:37:14 PM:       origin: config
11:37:14 PM:       package: netlify-plugin-gatsby-cache

Enhancement request: Add social icons for common social networks. (Facebook, Instagram, Twitter, etc)

Most sites these days include links to Social Media, using react-icons / FontAwesome svg icons.
It would be great if Foundation theme included support for these in the template.
I have added them myself to my site, example: https://rounduppromotions.netlify.app/
(However, I am a hack, so I'm sure it could be done more elegantly in the base theme.)
Here's a link to my repo if you want to see how I did it:
https://github.com/roundup-promotions/roundup-promotions-blog

Now all blog sites attribute a must essential on their post is tags. It becomes easy to find similar blog posts by the tags attached to them.

I see low quality images during lazy loading. Could you add blur effect?

So I cloned the repository via github first, to develop locally but when I did npm install and then gatsby develop, then after receiving the error below, I also did "gatsby new gatsby-starter-foundation https://github.com/stackrole/gatsby-starter-foundationin" but still in the end I ALWAYS receive the following ERROR

ObjectMiddleware.register: serializer for mini-css-extract-plugin/dist/CssModule/null is already registered

Error: ObjectMiddleware.register: serializer for mini-css-extract-plugin/dist/CssModule/null is already registered

• ObjectMiddleware.js:193 Object.register
  [moksgatsby]/[webpack]/lib/serialization/ObjectMiddleware.js:193:10

• index.js:182 Function.getCssModule
  [moksgatsby]/[mini-css-extract-plugin]/dist/index.js:182:34

• index.js:389 MiniCssExtractPlugin.apply
  [moksgatsby]/[mini-css-extract-plugin]/dist/index.js:389:44

• webpack.js:73 createCompiler
  [moksgatsby]/[webpack]/lib/webpack.js:73:12

• webpack.js:134 create
  [moksgatsby]/[webpack]/lib/webpack.js:134:16

• webpack.js:158 webpack
  [moksgatsby]/[webpack]/lib/webpack.js:158:32

• index.js:58 f
  [moksgatsby]/[webpack]/lib/index.js:58:16

• start-server.ts:173 startServer
  [moksgatsby]/[gatsby]/src/utils/start-server.ts:173:20

• task_queues.js:60 runNextTicks
  internal/process/task_queues.js:60:5

• timers.js:437 processImmediate
  internal/timers.js:437:9

• start-webpack-server.ts:44 startWebpackServer
  [moksgatsby]/[gatsby]/src/services/start-webpack-server.ts:44:7

not finished Building development bundle - 9.213s
not finished Caching HTML renderer compilation - 4.567s

https://stackrole.com/demos/foundation displays the following:

Hello. Thanks for the great starter theme. Clean and simple, just what I was hoping to find.

In setting it up for my own Netlify account, I found an error.

Deleting old blog posts and adding a new one breaks the path to the blog posts from the blog page, but not from the home page.

I created an example website to demonstrate the issue.

https://gatsby-starter-foundation.netlify.app/

I'm new to Gatsby, so though I will troubleshoot, I will probably move slow, so any help here will be greatly appreciated. TIA!

When navigating to the demo website on mobile, the pages render in dark mode by default. Is this preventable so that there is a uniform experience across mobile and desktop devices?

I wish the default template had comments feature as well.

I usually use Algolia search but I thought I would try lunar and found several errors in you code.

First in Gatsby config you have @gatsby-contrib/gatsby-plugin-elasticlunr-search listed under remark components move it to right above gatsby-plugin-sass, and configure it as in my repo listed below.

Then go to my repo and view my search component = complete rebuild at Bibwoe.com Repo

Lost of other tidbits of stuff included like tags, timeToRead ect. you might want to look at.

Happy Coding
Donald Boulton

When forking the latest commit of the gastby starter foundation, the Node version represented in the Netlify.Toml file does not match the current Node version represented in the .node-version file found in the root.

This is a simple update and I would like to be assigned this issue to resolve.

The featured image shows up nicely in the blog list displayed on the main page on iPhone, however when you click on a particular blog entry, the featured image is cropped as to be unusable.

blog-list.js uses:
featuredImage { childImageSharp { fluid(maxWidth: 540, maxHeight: 360, quality: 80)

blog-post.js uses:
Image = frontmatter.featuredImage ? frontmatter.featuredImage.childImageSharp.fluid

Wondering if there is an opportunity for improvement here?

Example, blog list, (iPhone) looks good:

Example, blog page,(iphone) looks bad:

Gatsby Starter Community Submissions

We would be happy to include your Starter as part of the Gatsby Community Starters Library! We review and add new starters to the Library on a monthly basis.

In order to be considered, your Starter should meet these minimum requirements:

[x] Be on the [latest major version of Gatsby](https://www.gatsbyjs.com/docs/reference/release-notes/)
[] Build without error on Gatsby Cloud
[] Have a demo deployed to Gatsby Cloud
[] Demonstrate best practices around accessibility
    [] For details and resources on accessibility standards, we recommend https://a11y.coffee/
[] Demonstrate best practices around performance
    [] For details and resources on performance, see:
    [] [Front-end performance (link)](https://web.dev/lighthouse-performance/)
    [] [Gatsby build performance (link)](https://www.gatsbyjs.com/docs/how-to/performance/improving-build-performance/)
[] Include documentation on installation and contribution

In addition to the guidelines above, we will also give preference to Starters that demonstrate use-cases, functionality, or designs not covered by existing Starters.

The gastby-plugin-netlify-cache that is listed in the netlify.toml is no longer supported and is deprecated.

This plugin has since been replaced with a new plugin called netlify-plugin-gatsby, having the user change the netlify.toml to use the new plugin, installing it, and then adding it to the Gatsby-config.js file.

Gastby-plugin-netlify is installed as a dev dependency.

Gastby Plugin Update

In the normal (light) mode the date is visible, but in the dark mode, the date is not visible.

 

Even after deleting the demo blogs posts they do appear at the bottom of other blog posts.
I tried to clear the cache and deployed again but still no change. any solution for this ?

Feature request : search integration.
Before anything else, I must tell you that this is the best 🥇 ever blogging theme I came across among all the gatsby stater themes. You guys deserve a big applause 👏 especially for making it a very mobile friendly as well 🥳 . I just wanted to make a feature request. Now a days every blogging site has a search facility. Particularly in this blog, I think it (search) will fit rightly in the hamburger menu (in the mobile edition). With that in place I think this blog will be unmatched in terms of features, design & performance/speed to any other Jam-stack blog. Kudos to you again.

Hi developers I have a feature request of adding a tags (#tags) in blogs so it'll be more easy for users to find the similar topic or subject by #tags.

Thank You!

Recommend changing /src/assets/scss/style.scss line 317, to color: #777

This grey color shows up nicely on both light or dark backgrounds.

running this -->
gatsby new gatsby-starter-foundation https://github.com/stackrole/gatsby-starter-foundation

results this

`
Error: Command failed with exit code 1: npm install

• error.js:60 makeError
  [lib]/[gatsby-cli]/[execa]/lib/error.js:60:11

• index.js:118 handlePromise
  [lib]/[gatsby-cli]/[execa]/index.js:118:26

• task_queues:95 processTicksAndRejections
  node:internal/process/task_queues:95:5

• init-starter.js:135 install
  [lib]/[gatsby-cli]/lib/init-starter.js:135:7

• init-starter.js:202 clone
  [lib]/[gatsby-cli]/lib/init-starter.js:202:3

• init-starter.js:343 initStarter
  [lib]/[gatsby-cli]/lib/init-starter.js:343:5

• create-cli.js:458
  [lib]/[gatsby-cli]/lib/create-cli.js:458:9
  `

$ gatsby new webgatsby-vdls https://github.com/stackrole/gatsby-starter-foundation
info Creating new site from git:
https://github.com/stackrole/gatsby-starter-foundation.git

Cloning into 'webgatsby-vdls'...
remote: Enumerating objects: 101, done.
remote: Counting objects: 100% (101/101), done.
remote: Compressing objects: 100% (89/89), done.
remote: Total 101 (delta 2), reused 60 (delta 1), pack-reused 0
Receiving objects: 100% (101/101), 24.51 MiB | 3.69 MiB/s, done.
success Created starter directory layout
info Installing packages...

npm ERR! code 1
npm ERR! path C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node-gyp rebuild
npm ERR! Les projets sont générés individuellement dans cette solution. Pour activer la génération en parallèle, ajoutez le commutateur "-m".
npm ERR! nothing.c
npm ERR! win_delay_load_hook.cc
npm ERR! nothing.vcxproj -> C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp\build\Release\nothing.lib
npm ERR! VError.cpp
npm ERR! C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp\src\libvips\cplusplus\VError.cpp(33,10): fatal error C1083: Impossible d'ouvrir le fichier include : 'vips/intl.h' : No such file or directory [C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp\build\libvips-cpp.vcxproj]
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | win32 | x64
npm ERR! gyp info find Python using Python version 3.11.0 found at "C:\Python311\python.exe"
npm ERR! gyp info find VS using VS2022 (17.4.33110.190) found at:
npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info spawn C:\Python311\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args 'C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'msvs',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp\build\config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\Users\fbeau\AppData\Local\node-gyp\Cache\18.12.1\include\node\common.gypi',
npm ERR! gyp info spawn args '-Dlibrary=shared_library',
npm ERR! gyp info spawn args '-Dvisibility=default',
npm ERR! gyp info spawn args '-Dnode_root_dir=C:\Users\fbeau\AppData\Local\node-gyp\Cache\18.12.1',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\Users\\fbeau\\AppData\\Local\\node-gyp\\Cache\\18.12.1\\<(target_arch)\\node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp',
npm ERR! gyp info spawn args '-Dnode_engine=v8',
npm ERR! gyp info spawn args '--depth=.',
npm ERR! gyp info spawn args '--no-parallel',
npm ERR! gyp info spawn args '--generator-output',
npm ERR! gyp info spawn args 'C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp\build',
npm ERR! gyp info spawn args '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args 'build/binding.sln',
npm ERR! gyp info spawn args '/clp:Verbosity=minimal',
npm ERR! gyp info spawn args '/nologo',
npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=x64'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe failed with exit code: 1
npm ERR! gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:201:23)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Windows_NT 10.0.22621
npm ERR! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd C:\Users\fbeau\gatsby\webgatsby-vdls\node_modules\sharp
npm ERR! gyp ERR! node -v v18.12.1
npm ERR! gyp ERR! node-gyp -v v9.1.0
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in:

ERROR UNKNOWN

Command failed with exit code 1: npm install

Error: Command failed with exit code 1: npm install

• error.js:60 makeError
  [npm]/[gatsby-cli]/[execa]/lib/error.js:60:11

• index.js:118 handlePromise
  [npm]/[gatsby-cli]/[execa]/index.js:118:26

• task_queues:95 processTicksAndRejections
  node:internal/process/task_queues:95:5

• init-starter.js:135 install
  [npm]/[gatsby-cli]/lib/init-starter.js:135:7

• init-starter.js:202 clone
  [npm]/[gatsby-cli]/lib/init-starter.js:202:3

• init-starter.js:343 initStarter
  [npm]/[gatsby-cli]/lib/init-starter.js:343:5

• create-cli.js:458
  [npm]/[gatsby-cli]/lib/create-cli.js:458:9

It would be interesting to know how you'd go about making the minimal changes to add a field for whether a blog post is live or not, it'd be nice to be able to edit and save w/o actually flipping the switch. I'd probably add an additional field to the template, but might also need to tweak the react.

If you go to the blog page and click on a blog, you get "Page Not Found"

If you click on the blog post from the home page, the post is found.

See: https://idmx268-cynthiateeters.netlify.app/blog

My site url redirect url redirect to trailing slash url but show only link without trailing slash.

https://gatsby-starter-foundation-9vk.pages.dev/bmnvbmvm this link redirect to https://gatsby-starter-foundation-9vk.pages.dev/bmnvbmvm/ this. how i show only link with trailing in the end

How do I change the language of the news date?

Hey,

I'm trying to install the gatsby-plugin-social9-socialshare plugin, both I get a version mismatch error on the gatsby plugin.
If I try to update that, I get a similar error on the react version.

Is there a guide on how to update the dependencies and bring them up to par to what they are now?

To reproduce an issue:

In the gatsby-node.js change the "postsPerPage" to a smaller value, e.g. 4.
Then after rebuild go to the blog-list page (/blog) and you'll see that the last page in pagination is empty.

Can you add a TikTok social media icon?

https://react-icons.github.io/react-icons/search?q=tiktok

I tried adding it myself, but TikTok profiles have the "@" symbol in them and that blows up the script.
For example, my TikTok profile is: https://www.tiktok.com/@charlie_hood
I tried replacing the "@" with %40 but that didn't help.

I got this working as follows:

1. gatsby new gatsby-starter-foundation https://github.com/stackrole/gatsby-starter-foundation
2. cd gatsby-starter-foundation
3. Per your suggestion, I edited the package.json file and removed the caret character from EVERY LINE (if I only removed from lines with netlify-cms in the name I still got the same error)
   
4. yarn install (instead of npm install)
5. gatsby develop

It now succeeds. I will plan on deploying this to Github Pages, so I'm hoping the updated package.json will be enough for github pages to build correctly.

Thanks for your assistance with this issue.

I followed the same steps with Node version v14, but I have received an error:

 gatsby develop
success open and validate gatsby-configs - 0.209s
warn Plugin gatsby-remark-images is not compatible with your gatsby version 3.1.2 - It requires gatsby@^4.0.0-next
success load plugins - 2.313s
success onPreInit - 0.076s
success initialize cache - 0.016s
success copy gatsby files - 0.157s
success onPreBootstrap - 0.034s
success createSchemaCustomization - 0.079s
success Checking for changed pages - 0.002s
success source and transform nodes - 0.398s
success building schema - 0.804s
info Total nodes: 139, SitePage nodes: 16 (use --verbose for breakdown)
success createPages - 0.120s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.102s
success update schema - 0.105s
success write out redirect data - 0.003s
success Build manifest and related icons - 0.228s
success onPostBootstrap - 0.236s
info bootstrap finished - 7.830s
success onPreExtractQueries - 0.002s
success extract queries from components - 1.712s
success write out requires - 0.016s
success run static queries - 0.048s - 3/3 62.57/s
success run page queries - 1.618s - 3/3 1.85/s

 ERROR 

Invalid options object. Ignore Plugin has been initialized using an options object that does not match the API schema.
 - options should be one of these:
   object { resourceRegExp, contextRegExp? } | object { checkResource }
   Details:
    * options misses the property 'resourceRegExp'. Should be:
      RegExp
      -> A RegExp to test the request against.
    * options misses the property 'checkResource'. Should be:
      function
      -> A filter function for resource and context.



  ValidationError: Invalid options object. Ignore Plugin has been initialized using an options object that does not match the API schema.
   - options should be one of these:
     object { resourceRegExp, contextRegExp? } | object { checkResource }
     Details:
      * options misses the property 'resourceRegExp'. Should be:
        RegExp
        -> A RegExp to test the request against.
      * options misses the property 'checkResource'. Should be:
        function
        -> A filter function for resource and context.
  
  - validate.js:105 validate
    [gatsby-starter-foundation]/[schema-utils]/dist/validate.js:105:11
  
  - create-schema-validation.js:16 
    [gatsby-starter-foundation]/[webpack]/lib/util/create-schema-validation.js:16:17
  
  - IgnorePlugin.js:28 new IgnorePlugin
    [gatsby-starter-foundation]/[webpack]/lib/IgnorePlugin.js:28:3
  
  - webpack-plugins.ts:14 Object.ignore
    [gatsby-starter-foundation]/[gatsby]/src/utils/webpack-plugins.ts:14:10
  
  - webpack-utils.ts:766 Object.moment
    [gatsby-starter-foundation]/[gatsby]/src/utils/webpack-utils.ts:766:42
  
  - webpack.config.js:200 getPlugins
    [gatsby-starter-foundation]/[gatsby]/src/utils/webpack.config.js:200:15
  
  - webpack.config.js:491 module.exports
    [gatsby-starter-foundation]/[gatsby]/src/utils/webpack.config.js:491:14
  
  - build-html.ts:139 buildRenderer
    [gatsby-starter-foundation]/[gatsby]/src/commands/build-html.ts:139:18
  
  - start-server.ts:113 createIndexHtml
    [gatsby-starter-foundation]/[gatsby]/src/utils/start-server.ts:113:28
  
  - start-server.ts:150 startServer
    [gatsby-starter-foundation]/[gatsby]/src/utils/start-server.ts:150:5
  
  - start-webpack-server.ts:44 startWebpackServer
    [gatsby-starter-foundation]/[gatsby]/src/services/start-webpack-server.ts:44:7
  

not finished Building development bundle - 0.127s

How can I solve it? It seems ifI install dependencies using npm there is a different error. How can I solve them? Are there any steps to follow?

Originally posted by @apoorvachikara in #27 (comment)