Troubleshooting

Troubleshooting

Here are some FAQ and most common pitfalls, may encounter while contributing.

Table of Contents

• Common Problems
  • Homestead
  • Artisan
  • Composer
  • NPM
  • Bower

Common Problems

Homestead

To ensure everything runs properly please verify that you installed the newest version Homestead as described in the Laravel Documentation. Also make sure that Vagrant uses the newest Homestead.box!

Artisan

...Module default not found...

As you do with databases in SQL connections, you can state a default module for the current session. All commands (which support or even need it) run against the specified module implicitly. To specify the default module type php artisan module:use MODULE.

See module:use Pull request with description.

...Module command module:migrate-rollback...

If you want to rollback a migration, you have to specify the module explicitly, otherwise the autoloader wont work and you will end up with an Class 'xyz' not found error.

See GitHub Issue.

Composer

...API rate limit...

• Due to the many dependencies you may encounter a GitHub API rate limit. Composer will prompt you to login with your GitHub account. Follow the instructions, if you are authenticated your rate limit is lifted.

...Composer.lock file...

• If you use composer install with an existing composer.lock file it will tell you that not the newest dependencies are installed, but the versions stated in composer.lock. To force an update (and also update the versions in the lockfile) use composer update.
• You can also use the flags --prefer-dist (use lockfile) or --prefer-source (newest version from packagist).

NPM

..access denied..

• NPM has to run as sudo.. always!

..other strange behavior using Windows..

• It is stated, that NPM has some problems with long Windows paths (even in the VM). Try to move the VM closer to your harddrive root and try again.

Bower

• Never run Bower as sudo!