Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when running 'yo jquery-boilerplate' #13

Closed
visualcookie opened this issue Apr 16, 2015 · 6 comments
Closed

Error when running 'yo jquery-boilerplate' #13

visualcookie opened this issue Apr 16, 2015 · 6 comments

Comments

@visualcookie
Copy link

Hi,

I get an error when running the generator. Below are some information about it.

Command run: yo jquery-boilerplate

Log:

  var files   = this.expandFiles('**/*', { cwd: this.sourceRoot(), dot: true }
                                                     ^
TypeError: undefined is not a function
    at new module.exports (/usr/local/lib/node_modules/generator-jquery-boilerplate/app/index.js:7:54)
    at Environment.instantiate (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:282:10)
    at Environment.create (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:259:15)
    at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:318:24)
    at /usr/local/lib/node_modules/yo/lib/cli.js:86:9
    at Environment.resolver.lookup (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/resolver.js:50:12)
    at init (/usr/local/lib/node_modules/yo/lib/cli.js:61:7)
    at pre (/usr/local/lib/node_modules/yo/lib/cli.js:48:3)
    at Object.<anonymous> (/usr/local/lib/node_modules/yo/lib/cli.js:150:1)
    at Module._compile (module.js:460:26)```
@kuldipem
Copy link

I am also getting this error.

@surajair
Copy link

me too

@edpittol
Copy link

edpittol commented May 7, 2015

+1

@visualcookie
Copy link
Author

I really hope that this repository isn't dead at all.

@seansean11
Copy link

+1 I'm not sure if this is the culprit, but according to npm the package is at version 0.1.2 which was released August 8. 2013 (npm page). And, according to the repo they just released version 0.2.0 last month. Looks like we are not installing the newest version.

@heldr
Copy link
Member

heldr commented May 14, 2015

@heldr heldr closed this as completed May 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants