Skip to content
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.

TypeError: args.includes is not a function #243

Closed
ludden007 opened this issue Mar 10, 2017 · 3 comments
Closed

TypeError: args.includes is not a function #243

ludden007 opened this issue Mar 10, 2017 · 3 comments
Assignees

Comments

@ludden007
Copy link

Hi... I followed the install instructions for generator-keystone (v0.5.0), and when trying to create a project, received a "TypeError: args.includes is not a function". I downgraded geneator-keystone to v0.4.2 and it's now working, so something in 0.5.0 is causing this. Cheers.

$ yo keystone
/usr/local/lib/node_modules/generator-keystone/app/index.js:14
	this.auto = args.includes('auto');
	                 ^

TypeError: args.includes is not a function
    at new KeystoneGenerator (/usr/local/lib/node_modules/generator-keystone/app/index.js:14:19)
    at Environment.instantiate (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:336:10)
    at Environment.create (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:313:15)
    at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:372:24)
    at /usr/local/lib/node_modules/yo/lib/cli.js:140:11
    at Array.forEach (native)
    at /usr/local/lib/node_modules/yo/lib/cli.js:139: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:115:7)
    at pre (/usr/local/lib/node_modules/yo/lib/cli.js:73:3)
$ yo doctor

Yeoman Doctor
Running sanity checks on your system

✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version
@ftabaro
Copy link

ftabaro commented Mar 12, 2017

same here.

 node 4.2.6
 npm 3.5.2
 yo 1.8.5
 mongo 2.6.12

I actually noticed they updated yo repository couple of days ago, it may be relevant.

@Noviny
Copy link
Contributor

Noviny commented Mar 12, 2017

I did some digging in to this, and it appears to be with older versions of node. I am not experiencing the problem on node 6.3.1. It wasn't our intent to stop supporting older versions of node, so I'll get a fix out for this.

@JedWatson
Copy link
Member

Closed by #244

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants