sstringer's avatar

Should I require Laravel itself when developing a package?

I'm developing my first Laravel package and have a question about composer dependencies. Namely, is it necessary/desirable to declare Laravel itself as a dependency? I'm thinking I need to limit it to Lvl 5.2+, but the documentation isn't clear about how to accomplish this.

Thanks, Steve

0 likes
2 replies
primordial's avatar

@sstringer I would say, yes. But Laravel is itself made up of many packages. I have recently published a package that is specific to illuminate/database. Perhaps your package could be more specific than just "Laravel"?

willvincent's avatar

In the packages I've built I require the portions necessary..

my feeds package has this:

"illuminate/support": "~5.0",

my laravel-rateable package has this:

"illuminate/support": "~5.0",
"illuminate/database": "~5.0"
1 like

Please or to participate in this conversation.