Smartypants | page clone of Genius.com , built using Rails | Frontend Framework library

From what I understand, Ruby moves all stdlib parts into gems, some are "default gems", as in, they are normally installed with Ruby and don't need a reference in your Gemfile, but some are "bundled gems" which also are installed with Ruby, but need a reference in Gemfile. The problem stems from a fact, that with every Ruby release, some "default gems" become "bundled gems".

Such a situation happened with webrick in the past.

In your case it's most likely that you need rexml, which just became a "bundled gem" in Ruby 3.0: https://stdgems.org/rexml/

All this about a theory, but a solution is pretty simple. You just need to do

The problem is that you have Node 17.2.0. locally but in Netlify's environment, you are running a lower version (by default it's not set as 17.2.0). So the local environment is OK, Netlify environment is KO because of this mismatch of Node versions.

When Netlify deploys your site it installs and builds again your site so you should ensure that both environments work under the same conditions. Otherwise, both node_modules will differ so your application will have different behavior or eventually won't even build because of dependency errors.

You can easily play with the Node version in multiple ways but I'd recommend using the .nvmrc file. Just run the following command in the root of your project:

I had the same problem and I found a workaround here at https://github.com/jekyll/jekyll/issues/8523

Add gem "webrick" to the Gemfile in your website. Than run bundle install

At this point you can run bundle exec jekyll serve

For me it works!

The problem got solved after including gfm.min.css

Azure Devops Pipelline Jekyll Build Failure

If you are using the private agent, please try to following steps to resolve this error:

• Running bundle info kramdown will give you the path to where kramdown has been installed.
• Run gem env to get an insight on all paths Ruby is concerned about.
• If the directory where kramdown got installed from above isn't listed in the gem env output, you'll have to manually add that path

If you are using the hosted agent, please try to reference following suggestions：

Add gem "webrick" to the Gemfile in your website. Than run bundle install

At this point you can run bundle exec jekyll build

In the Blog class you need a / in your component at to={blog${node.fields.slug}}

So {/blog${node.fields.slug}}

Without that it'll take the relative path 👍

(I've left out the extra set of backticks as it mucks up the formatting on stack overflow, but they should still be there)

You are most likely seeing this issue because there are no markdown files found at any of the paths that gatsby-source-filesystem is pointing to in gatsby-config.js

According to nihgwu's comment on this issue:

the MarkdownRemark node type will only be created when there is a markdown node, or there will be no MarkdownRemark node type at all, so you can't query allMarkdownRemark

To solve your issue, make sure that there is as least one markdown file found in the ${__dirname}/content/blog folder.

If you do have markdown files in a different folder, make sure to add that location as another gatsby-source-filesystem entry in your gatsby-config.js.

Since both markdown and images are in the same directory you can simply specify the image like below

I am more interested in how do you call those images in your components rather than in the package.json (it doesn't seem a dependencies issue) because inspecting the code, it seems that you've added the /static path which is not required. As it is shown in the following screenshot:

Regarding the updates coming from the comments below, we've figured out that the issue is related directly to this GitHub issue where apparently images retrieved by a markdown are blurring. What solves the issue is to pass a withWebp parameter in Gatsby's configuration, so in gatsby-config.js: