[GH-ISSUE #857] Monolog require-dev on elastica? #334

New issue

Closed

opened 2026-03-04 02:14:13 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 02:14:13 +03:00

Owner

Originally created by @laszlof on GitHub (Sep 27, 2016).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/857

Hello,

Is there a particular reason there is a require-dev on elastica? My understanding is that require-dev is used for development tools. Elastica perhaps belongs as a "suggest" as you have it, but I do not believe it should be a require-dev. This is causing issues with one of our packages currently. (See composer issue: https://github.com/composer/composer/issues/5727)

Thanks.

Originally created by @laszlof on GitHub (Sep 27, 2016). Original GitHub issue: https://github.com/Seldaek/monolog/issues/857 Hello, Is there a particular reason there is a require-dev on elastica? My understanding is that require-dev is used for development tools. Elastica perhaps belongs as a "suggest" as you have it, but I do not believe it should be a require-dev. This is causing issues with one of our packages currently. (See composer issue: https://github.com/composer/composer/issues/5727) Thanks.

kerem closed this issue

2026-03-04 02:14:13 +03:00

kerem commented

2026-03-04 02:14:14 +03:00

Author

Owner

@stof commented on GitHub (Sep 27, 2016):

well, it is necessary to have elastica during development to run the testsuite fully. It probably also belongs to suggestions.

require-dev is a root-only property. So it cannot cause any issue in your package. It is totally ignored anywhere else than when working on monolog itself.

@stof commented on GitHub (Sep 27, 2016): well, it is necessary to have elastica during development to run the testsuite fully. It probably _also_ belongs to suggestions. `require-dev` is a root-only property. So it cannot cause any issue in your package. It is totally ignored anywhere else than when working on monolog itself.

kerem commented

2026-03-04 02:14:14 +03:00

Author

Owner

@laszlof commented on GitHub (Sep 27, 2016):

We commit our lock file, and the require-dev for elastica is ending up in our root level composer.lock file.

@laszlof commented on GitHub (Sep 27, 2016): We commit our lock file, and the require-dev for elastica is ending up in our root level composer.lock file.

kerem commented

2026-03-04 02:14:14 +03:00

Author

Owner

@laszlof commented on GitHub (Sep 27, 2016):

This appears to be an unrelated issue. Closing.

@laszlof commented on GitHub (Sep 27, 2016): This appears to be an unrelated issue. Closing.

kerem commented

2026-03-04 02:14:14 +03:00

Author

Owner

@nicolashohm commented on GitHub (Nov 14, 2016):