Hi,

I was thinking, is it necessary to require illuminate/support in composer.json?

1. This started because my project is still relying on version 8
2. As this skeleton is meant to create Laravel packages, I think it is safe to assume the parent project already includes the "correct" version of illuminate/support
3. If the new package is installed in non-Laravel projects, I suspect illuminate/support is still not enough
4. My view is to remove since it doesn't help that much and in fact, becomes a line that requires constant maintenance

Thank you.

Is there any reason for it being there? It doesn't actually work

Title Says it all and it effectively breaks the Packager

Its more of a question as to why verses it being a issue/bug.

I'm curious as to why you prepend the package name to the publish group.

// Publishing the configuration file.
$this->publishes([
      __DIR__.'/../config/:lc:package.php' => config_path(':lc:package.php'),
], ':lc:package.config');

Why not just use "config" as the group? Then in the publish command its '--tag="config"' verses '--tag="mypackage.config"

I am already specifying the package in the publish command.

I know i can just easily change it, but i'm curious as to the reason behind the naming convention.

Illuminate support of v5 is causing the main generator to hang since Illuminate is now on v6.

Does it make sense to change and expand this line in the ServiceProvider from

To

// $this->loadRoutesFrom(__DIR__.'/routes.php'); // packager
// $this->loadRoutesFrom(__DIR__.'/../routes/web.php'); // Laravel convention
// $this->loadRoutesFrom(__DIR__.'/../routes/api.php'); // Laravel convention
// $this->loadRoutesFrom(__DIR__.'/../routes/console.php'); // Laravel convention