Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Greenkeeper builds fail due to our caching method for node_modules

Open
#1,382 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
ci-cd

Research direction

Start by reproducing a Greenkeeper build and inspect the configuration responsible for caching node_modules, especially how the dependency-cache key is generated and restored. The issue is done when the cache restores successfully and future Greenkeeper builds no longer fail because no cache is found.

Written by the indexing model from the issue text.

Description

bug

Quoting https://github.com/code-corps/code-corps-ember/pull/1381#issuecomment-330734655

Something in the way we're doing caching of our node_modules is broken here.

You can see when the restore tries to happen that it fails:

No cache is found for key: dependency-cache-+kGUB3JuQQmksW+LUxPJerNDS37R6sDf8daIJCOw8FY=-8HTuZ8asTuy34o5mEvgz3dI7FaVDhbZL6IKcXolKMvM=

I'm not sure which part of this key is broken precisely or why, but it needs investigating. This will happen with all future Greenkeeper builds if not found and fixed.

Dominant language
JavaScript
Stars
120
Forks
75
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.