heroku / heroku/heroku-buildpack-nodejs
NPM_CONFIG_PRODUCTION presence causes cache to not work in monorepos for yarn
Open
needs investigation
yarn-2
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 2.6k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 30
Description
If NPM_CONFIG_PRODUCTION is set, then the buildpack falls into an if statement that causes the cache to not be stored properly.
Contributor guide
Research direction
Start by tracing the buildpack's cache handling and the conditional affected by NPM_CONFIG_PRODUCTION when Yarn is used in a monorepo. Reproduce the issue with that environment variable set, then verify that the expected cache is stored and reused without it changing unrelated build behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100