Fixed missing dependencies issue by updating Gemfile

[sa-fw-an]

When running bundle exec jekyll serve --incremental, an error occured. Investigation reveals that the issue is due to missing dependencies in the Gemfile, which was introduced by Commit 1dd0e41. The changes in this commit removed essential dependencies, leading to this error.

• Fixes Error running bundle exec jekyll serve --incremental due to missing dependencies while set up #670

[sa-fw-an]

@pikurasa Ive created a new pr. Please review this

[quozl]

That's a future deprecation warning, not an error. Issue closed.

You're apparently updating the dependencies using one of the steps mentioned in
#634 (comment)

But without the other steps, this change would likely break the web site deployment build.

[sa-fw-an]

Hi @quozl,
I've attached a screenshot of the error that occurs when running bundle exec jekyll serve --incremental

Error Screenshot:

---

After investigating, I found that the issue was caused by missing dependencies. To resolve this, I had raised a PR that fixes the problem. Please review it.
To troubleshoot, could you try setting up the dev environment again after removing all locally installed gems? This will help verify if the error persists.
Others have encountered the same issue, and it's likely that PR

• delete Gemfile.lock from repository #525

introduced the problem. I look forward to your response.

Best regards.

[quozl]

As I said, we're using Jekyll 3, and moving to Jekyll 4 as you have suggested will be a complex process that risks the build and deploy of the web site. I don't see any sign that you know what you are talking about in the context of that process.

While you may be happy with the fix to your own environment, that's not the environment we work with.

[pikurasa]

I've reviewed the PR, and I don't quite see where this PR would move us to Jekyll 4.

While we might not know for certain if it would work on GH if merged, FWIW it does work on my machine.

Also, in some ways it seems like a simplification, since it is removing constraints on which versions to load. So I assume that whatever setup you have, your system resolves the dependencies on its own.

So, I'm not totally certain yet that we write this PR off.

That said, I never encountered the issue. So it's value is mainly in helping contributors using Mac/Windows up and running with fewer problems, and it doesn't solve any pressing issues with deployment.

[sa-fw-an]

I've reviewed the PR, and I don't quite see where this PR would move us to Jekyll 4.

While we might not know for certain if it would work on GH if merged, FWIW it does work on my machine.

Also, in some ways it seems like a simplification, since it is removing constraints on which versions to load. So I assume that whatever setup you have, your system resolves the dependencies on its own.

So, I'm not totally certain yet that we write this PR off.

That said, I never encountered the issue. So it's value is mainly in helping contributors using Mac/Windows up and running with fewer problems, and it doesn't solve any pressing issues with deployment.

@pikurasa Yes they would automatically solve the dependency errors. Also new begginers wouldn't be facing issue they are facing now if this is merged. Can i go ahead with a new pr ?

[quozl]

I've not yet found a good reason to move to Jekyll 4. New beginners could use the Docker set up by @MostlyKIGuess, but the biggest mistake seems to be their choice of task; mostly cosmetic. Changes to content in response to changes in the environment, code, or use of Sugarizer, Music Blocks, or Sugar would be more welcome.

You can have more than one pull request open at a time, that's your choice. Just don't mix the branches and be ready to rebase when master branch moves. It's a skill.