freyskeyd/generator-laravel

Get the power of yeoman with laravel. Manage Grunt, Bower, Tests and many stuff like a boss.

DEPRECATED

THIS REPOSITORY NEED A NEW MAINTAINER

I don't use atom for a while... like 2years and i don't have time to maintain this repository. If someone wants to be involved, just drop me an email.

Generator-laravel

A generator for laravel (with Yeoman).

Getting started

• Make sure you have yo installed: npm install -g yo

• Install the generator: npm install -g generator-laravel

• Run: yo laravel

• yo laravel => Starting point

You can

• Install laravel in current folder or any folder
• You can define multiple database configuration with environment

Known Issues

• Windows Err with composer #1

Todo

• Many things...

License

MIT License

generator-laravel's Issues

Does this have a built in server process?

If not, what are the possibilities of adding a built in PHP server (maybe FastCGI)? And maybe do something like grunt server and it'd launch browser on 127.0.0.1:9000 like
https://github.com/yeoman/generator-webapp

Composer missing

$ yo laravel:install ./
[?] Are you sure about cleaning and installing in ./?: Yes
 conflict Composer is missing

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:980:11)
    at Process.ChildProcess._handle.onexit (child_process.js:771:34)

I'm guessing my yo install is funky? Any help appreciated ;)

conflict Laravel error

Hi, I know that this is a work in progress, but maybe this can help you debugging. I got this error while installing:

...
     info composer : Script php artisan clear-compiled handling the post-install-cmd event returned with an error
 conflict Laravel error 

                      
  [RuntimeException]  
  Error Output:       
                      



 conflict Laravel error create-project [-s|--stability="..."] [--prefer-source] [--prefer-dist] [--repository-url="..."] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-scripts] [--no-progress] [--keep-vcs] [--no-install] [package] [directory] [version]



     info Laravel installed 

I am using OS X BTW.

Unhandled 'error' event

Windows 7 32bit with PowerShell.
yo webapp works fine.

PowerShell> yo laravel:install C:\Users\66beta\Desktop\myo
[?] Are you sure about cleaning and installing in ./?: Yes
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:980:11)
    at Process.ChildProcess._handle.onexit (child_process.js:771:34)

.stdout.on() being called multiple times

Disclaimer: I am no expert with many of the technologies involved, but I have a pretty good handle on concepts. With that out of the way...

I have your generator installed, and I am also using it as inpiration for some of my own generators. I started having errors within my sub-generators with race conditions on async();

Long story short: The event listeners for the stream outputs are being set and called multiple times:

  composer.stdout.on('data', function () {
    self.info(chalk.green('Composer has been found'));
    self.composer = true;
    cb();
  });

and:

    composer.stdout.on('data', function (data) {
      self.info(chalk.green('composer: ') + (data.toString().replace(/\n/g, '')));
    });

So within your generator the first event listener is being called a second time, and in turn, the async is being called again. Within your generator it isnt a problem - the install is the last in the list. Within my sub generator its causing the main generator to fire back up early and call the callback twice. It took me a while to track down this as the problem - helped me learn a lot about how everything links together!

Suggestion

Changing these readouts to composer.stdout.once() will not hold a
reference to the listener further down the chain.

(this doesnt have a direct effect on your generator, but it may help you or others further down the line)

Thanks!

Grunt and Bower configs dont seem to get installed?

Am I doing something wrong? no gruntfile, package.json or bower.json. Perhaps your description is misleading?

"#_ is deprecated. Require your own version of Lodash or underscore.string"

Node v4.4.6
Yo v1.8.4
MacOS Sierra beta 2
Composer installed

(!) require('yeoman-generator').generators.Base is deprecated. Use require('yeoman-generator').Base directly
(!) require('yeoman-generator').generators.Base is deprecated. Use require('yeoman-generator').Base directly
(!) #_ is deprecated. Require your own version of Lodash or underscore.string
events.js:141
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read property 'chain' of undefined
    at LaravelGenerator.rootMenu (/usr/local/lib/node_modules/generator-laravel/app/index.js:23:29)
    at Object.<anonymous> (/usr/local/lib/node_modules/generator-laravel/node_modules/yeoman-generator/lib/base.js:439:23)
    at /usr/local/lib/node_modules/generator-laravel/node_modules/run-async/index.js:26:25
    at /usr/local/lib/node_modules/generator-laravel/node_modules/run-async/index.js:25:19
    at /usr/local/lib/node_modules/generator-laravel/node_modules/yeoman-generator/lib/base.js:440:9
    at processImmediate [as _immediateCallback] (timers.js:383:17)

TypeError: Cannot read property 'bold' of undefined

On a fresh install of Yeoman version 1.0.4, npm version 1.3.5 and node 0.10.5, I'm getting the following error

/usr/local/lib/node_modules/generator-laravel/node_modules/yeoman-generator/lib/util/common.js:5
'\n `---------´ | ' + 'Welcome to Yeoman,'.yellow.bold + ' |' +
^
TypeError: Cannot read property 'bold' of undefined
at Object. (/usr/local/lib/node_modules/generator-laravel/node_modules/yeoman-generator/lib/util/common.js:5:56)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/local/lib/node_modules/generator-laravel/node_modules/yeoman-generator/lib/base.js:91:26)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)

This is most likely caused by the same issue as this:

• yeoman/generator-mobile/issues/10

and I tried updating my local packages.json, but that didn't work.