Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pruning devDependencies asks me to remove and reinstall from scratch. #49

Open
gio-shara-code opened this issue Jan 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@gio-shara-code
Copy link

Describe the bug
I am trying to deploy a landing page (next.js app) to heroku using monorepo architecture. The problem occurs while pruning devDependencies. It tries to receive an input whether the devDependencies can be removed.

To Reproduce
Steps to reproduce the behavior:

  1. turbo build --filter=landing-page

Versions (please complete the following information):

  • Heroku Stack: heroku/8.7.1

  • Node Version: 20.11.0

  • PNPM Version: 8.15.0

  • turbo Version: ^1.11.3

Additional context

remote: -----> Pruning devDependencies
remote:        ? The modules directory at "/tmp/build_bbb22d47/apps/backend/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ ? The modules directory at "/tmp/build_bbb22d47/apps/console/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ ? The modules directory at "/tmp/build_bbb22d47/packages/ts-config/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ ? The modules directory at "/tmp/build_bbb22d47/packages/ui/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ ? The modules directory at "/tmp/build_bbb22d47/apps/client/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ ? The modules directory at "/tmp/build_bbb22d47/apps/landing-page/node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n) ‣ (node:2325) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 keypress listeners added to [ReadStream]. Use emitter.setMaxListeners() to increase limit
remote:        (Use `node --trace-warnings ...` to show where the warning was created)
remote:        
remote: -----> Build succeeded!
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote: 
remote: -----> Compressing...
remote:  !     Compiled slug size: 512.6M is too large (max is 500M).
remote:  !     See: http://devcenter.heroku.com/articles/slug-size
remote: 
remote:  !     Push failed
remote: Verifying deploy...
remote: 
remote: !       Push rejected to prayers-landing-page.

This is my folder architecture:
Screenshot 2024-01-29 at 21 06 15

Describe the solution you'd like
I would like to force-prune the devDependencies. Or default set the answer yes. Don't know if it's even possible but throwing it out there.

@gio-shara-code gio-shara-code added the bug Something isn't working label Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant