Skip to content

Fix Heroku build: move dotenv-flow to production dependencies#2

Draft
Copilot wants to merge 2 commits intov6.9.4_productionfrom
copilot/fix-heroku-build-issues
Draft

Fix Heroku build: move dotenv-flow to production dependencies#2
Copilot wants to merge 2 commits intov6.9.4_productionfrom
copilot/fix-heroku-build-issues

Conversation

Copy link

Copilot AI commented Mar 14, 2026

Heroku sets NODE_ENV=production, so npm install skips devDependencies. dotenv-flow is required at the top of lib/rammerhead/src/build.js but was listed as a devDependency, causing the build to fail.

  • Moved dotenv-flow from devDependencies to dependencies in lib/rammerhead/package.json

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…merhead

On Heroku, npm install skips devDependencies by default (NODE_ENV=production).
Since dotenv-flow is required by src/build.js during the build step, it must
be a production dependency to be available during Heroku builds.

Co-authored-by: nota9x <105396031+nota9x@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix build issues in Heroku due to missing module Fix Heroku build: move dotenv-flow to production dependencies Mar 14, 2026
Copilot AI requested a review from nota9x March 14, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants