keystonejs/generator-keystone

⚠️ Archived - Legacy KeystoneJS project generator for Yeoman

generator-keystone's Issues

404 Errors inside Dashboard

Amazing work on this generator. I was able to install it and get it running quickly. Very impressed with Keystone so far!

I'm running into an issue after running the generator, where, when I sign into the dashboard/admin section, the links for galleries, enquiries, and users seem to reach a 404 page. I'm also encountering this
issue when attempting to create a new item.

The path from each link appears as:
http://localhost:3000/keystone//keystone/galleries

Obviously, the keystone//keystone is causing the issue. I thought I'd try and fix this myself but am not seeing where these paths are being set. Also curious if anyone else has encountered this.

Generator fails on Windows 8 cygwin

I get the following error when trying to run the generator

Mike@Mike-VAIO /cygdrive/c/workspaces/web
$ yo keystone

Welcome to KeystoneJS.


net.js:156
    this._handle.open(options.fd);
                 ^
Error: EINVAL, invalid argument
    at new Socket (net.js:156:18)
    at process.stdin (node.js:664:19)
    at Object.Interface.createInterface (C:\Users\Mike\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-generator\node_modules\inquirer\node_modules\readline2\index.js:31:43)
    at PromptUI.UI (C:\Users\Mike\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-generator\node_modules\inquirer\lib\ui\baseUI.js:23:40)
    at new PromptUI (C:\Users\Mike\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-generator\node_modules\inquirer\lib\ui\prompt.js:26:8)
    at Object.inquirer.prompt (C:\Users\Mike\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-generator\node_modules\inquirer\lib\inquirer.js:39:10)
    at TerminalAdapter._prompt [as prompt] (C:\Users\Mike\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-generator\lib\env\adapter.js:36:19)
    at KeystoneGenerator.Base.prompt (C:\Users\Mike\AppData\Roaming\npm\node_modules\generator-keystone\node_modules\yeoman-generator\lib\base.js:186:20)
    at KeystoneGenerator.prompts (C:\Users\Mike\AppData\Roaming\npm\node_modules\generator-keystone\app\index.js:130:7)
    at C:\Users\Mike\AppData\Roaming\npm\node_modules\generator-keystone\node_modules\yeoman-generator\lib\base.js:387:14

ERROR: node-sass not found.

So I've just used the generator to build a new site and selected sass for stylesheets. It said everything was ready to run, but it errors with:

> node keystone.js

ERROR: node-sass not found.

Please install the node-sass-middleware from npm to use the `sass` option.
You can do this by running "npm install node-sass-middleware --save".

If I install it as it says it works fine.

I also tried to just install node-sass but that still fails with the same message. (I was looking at keystonejs/keystone#183 (comment))

I probably wont have time to do a PR for this, so thought I'd just raise it!

Multiple errors in Swig templates

Unfortunately the swig generator doesn't produce a working example. Looks like one ternary operator was fixed in bddda76 but here are some other issues I've noticed:

views/blog.swig:14 - for loop is never closed
views/blog.swig:111 - if is never closed
views/blog.swig:118 - ternary operator
views/contact.swig:* - many invalid ternary operators

Sometimes it's hard to catch or fix these things because tag indentation doesn't match. I am curious to know the method behind the indentation.

Thanks for the great project!

yo keystone fails with "TypeError: Object #<Object> has no method 'tmpdir'" (fix)

Greetings,
following up the instructions to install keystonejs starting from a fresh npm tree with latest stable nodejs (v0.10.25) I got

$ yo keystone
TypeError: Object #<Object> has no method 'tmpdir'
    at Object.<anonymous> (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/tempfile/index.js:3:28)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/decompress.js:12:16)
    at Module._compile (module.js:449:26)

searching around I found out is due to stupid api change from recent version of node
tmpdir is now tmpDir()
so I quickly fixed editing
/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/tempfile/index.js
var tmpdir = require('os').tmpDir();
I don't know if this is the right place to report the issue since is the tempfile module but I'm not confident on how the dependencies in yeoman get injected and it may become useful for anyone stumbling upon this issue.

bootstrap glyphicons fonts path is wrong

according to bootstrap/_variables.scss the glyphicons fonts are expected to live in <project_root>/public/fonts/bootstrap/ — however the generator puts them in <project_root>/public/fonts/.

Add support for custom models

As suggested by @JedWatson in Keystone #88, add support for generating custom models.

eg:

key? Post
fields? title String, content Html wysiwyg:true, published:Boolean, author Relationship ref:User
autokey? from:title key:slug unique:true
map? name:title

how about including front-end framework and choosing bootstrap options?

1. I was thinking that view api couldn't give a enough controller even if it has very awesome apis such as 'init' or render or 'restful'.
   But Some heavy sites need more events such as click or others like that.
   So, how about giving a choice to include a front-end framework( angular or backbone ) or not. It could be a issue about original Keystone itself.
2. (it also could be a issue about original Keystone itself). How about giving a choice bootstrap or not? there are so many times I want to use other framewokrs not bootstrap (using bower can be a great option).

Thank you!

possible npm version issue

Deploying a generated app from this generator on digital ocean with dokku failed for me unless I set a newer npm version explicitly in the package.json. Otherwise it will run into this https protocol issue npm/npm#2119. I'm not sure if this is a dokku/docker issue or due to the way npm is set in the package.json. Same app will work fine deployed to heroku.

Generator fails if new directory selected

I just updated the generator, and now I get an error - not sure if it was there before my udpate.
Running the generator in window 8.1 in git bash.

If I select Y for create new directory option, any answer I give for mandrill (next question) causes an exception to be thrown in console.

The error seems to be in index.js on line 180 on a call to slugify. I'll see if I have a sec to read through (was only testing the generator), but figured I would report it first.

Here is the error:

C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:9048
                throw e;
                      ^
TypeError: Object function lodash(value) {
      // don't wrap if already wrapped, even if wrapped by a different `lodash` constructor
      return (value && typeof value == 'object' && !isArray(value) && hasOwnProperty.call(value, '__wrapped__'))
       ? value
       : new lodashWrapper(value);
    } has no method 'slugify'
    at KeystoneGenerator.<anonymous> (C:\Users\Erik\AppData\Roaming\npm\node_modules\generator-keystone\app\index.js:180:27)
    at PromptUI.onCompletion (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\lib\ui\prompt.js:69:10)
    at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.completed (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1775:12)
    at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1712:14)
    at AutoDetachObserverPrototype.completed (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:9068:31)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1712:14)
    at AnonymousObserver._onCompleted (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:2801:56)
    at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.completed (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1775:12)
    at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1712:14)
    at AutoDetachObserverPrototype.completed (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:9068:31)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (C:\Users\Erik\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\node_modules\inquirer\node_modules\rx\dist\rx.all.js:1712:14)

Error: could find module after "yo keystone"

Lots of modules are not installed even I did "npm install".
They are not listed in the package.json

Such as cookie-jar, qs, oauth-sign, hawk, aws-sign, http-signature and so on.

Create additional routes + views

Would prompt for route name, some basic settings, then generate the required files and explain how to integrate it with the app.

Prompt for mongodb URI or check mongo availability

As pointed out by @subhog in keystonejs/keystone-classic#272, yo keystone should prompt for the default mongodb connection URI and if it's local, check that the mongod process is running before it completes.

If the mongo connection is not available, it should include instructions to start it before the 'start your app with node keystone line.

Missing Pagination Button Styles from Demo

Problem

While adding pagination functionality I noticed a styling issue with the previous and next buttons.

Live Demo Site

A generated keystone demo app (hbs & jade) are missing the entypo styles and have the following look

It appears that this keystone-demo: optimising homepage added entypo styles and font to the live demo. But the styles were never added to generator.

Should the entypo styles be added to the generator? Or are there bootstrap options we can use instead?

Cookie secret should not be commited to the repo

I've noticed some people not hiding it, which means we probably shouldn't generate it into the keystone.js file. Maybe .env would be a better home for it... or we should at least add a warning comment above it.

Many "WARN unmet dependency" when I use "npm install -g generator-keystone"

[root@localhost keystone]# npm install -g generator-keystone
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/insight requires chalk@'~0.4.0' but will load
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/file-utils requires glob@'~3.2.6' but will load
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/findup-sync requires glob@'~3.2.9' but will load
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yosay/node_modules/strip-ansi requires ansi-regex@'^0.1.0' but will load
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yosay/node_modules/ansi-regex,
npm WARN unmet dependency which is version 0.2.1
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yosay/node_modules/taketalk requires minimist@'^0.1.0' but will load
npm WARN unmet dependency /usr/lib/node_modules/yo/node_modules/yosay/node_modules/minimist,
npm WARN unmet dependency which is version 0.2.0
[email protected] /usr/lib/node_modules/generator-keystone
?..?� [email protected]
?..?� [email protected]
?..?� [email protected] ([email protected], [email protected], [email protected])
?..?� [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
[root@localhost keystone]# yo keystone
-bash: yo: command not found

Yeoman generator errors

Sorry to report I was unable to install Keystone using Yeoman generator, getting "silly lockfile" errors during installation process: npm-debug.log is 137 lines long - it worked fine until line 90 but every packages from 'grunt-node-inspector' is getting same "silly lockfile" error. The funny part is Yeoman not seing the problem still propose to start the project after node modules installation failed. Doing so I got missing module errors indeed. I would need to install keystone manually like a regular node project — how do we do that?

Email doesn't work

I have created an app with all the default settings (including the test Mandrill API key), but when I try and send a contact message the app crashes:

TypeError: undefined is not a function
  at [object Object].<anonymous> (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:552:11)
  at [object Object].Email.buildOptions (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:368:10)
  at [object Object].<anonymous> (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:341:22)
  at [object Object].<anonymous> (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:246:3)
  at [object Object].<anonymous> (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:312:3)
  at [object Object].<anonymous> (/Users/kumo/Projects/Heroku/email/my-site/node_modules/keystone/lib/email.js:283:11)
  at fs.js:271:14
  at Object.oncomplete (fs.js:107:15)

I tried to use node-debug but all I could see was that callback appeared to be undefined.

Dynamically populate new user details in the templates

Since we added the ability to configure your default admin email and password, we should also make the information on the default home template dynamic to reflect the details entered.

Add brunch support (JS Task Runner)

http://blog.toggl.com/2014/03/grunt-vs-gulp-vs-brunch/

Small problem with nunjucks loop.index in generated post page

Came a cross a small thing with the generated nunjucks code on the post page.

It says

{% if loop.index < page.categories.length -1 %},{% endif %}

but I think it should say

{% if loop.index < page.categories.length %},{% endif %}

since according to this http://mozilla.github.io/nunjucks/templating.html

nunjucks loop.index is 1 indexed whereas nunjucks loop.index0 is 0 indexed.

I was left wondering (for a few minutes anyway) why my categories weren't separated by commas.

:)

Add gulp to generated projects

As mentioned by @thechunsik on twitter, we should add a default grunt / gulp config to generated sites.

Ideally, it would be offered as another question: "Would you like to include gulp config" during setup.

Keystone itself uses gulp, so it's probably better to keep things consistent and avoid developers having to install / learn / use both.

Maybe better would be to support both (if they can be equivalent, not sure if this is possible) and offer the user during setup "Would you like to include gulp or grunt? (enter: gulp / grunt / default: none)" - this way developers comfortable with one or the other could use the one they prefer.

Further support for alternative view engines

Love Keystone.

I was wondering though, would it be possible to add a question on what views engine we would prefer? (Default: Jade, options like EJS etc.)

Not a fan of Jade personally (think it is a love it or hate it thing) and something like an option to automatically scaffold EJS would be a great time saver.

Add email notifications for new enquiries

It's a common requirement, and would be a good demo of how to setup / use the Email functionality in Keystone.

Error when handlebars used for generating

Got an error after try to start (node keystone) keystone with fresh generated KeystoneJS and Handlebars as a templating language. With Jade everything works fine.
Error: getaddrinfo ENOTFOUND
at errnoException (dns.js:37:11)
at Object.onanswer as oncomplete

Version bump causes installation to fail

The new dependencies added today for v0.2.0 cause npm install -g generator-keystone to fail on a fresh install of Ubuntu 14.04.

npm http 304 https://registry.npmjs.org/es6-iterator
npm http 304 https://registry.npmjs.org/es6-symbol
npm http GET https://registry.npmjs.org/yo
npm http 304 https://registry.npmjs.org/yo
npm ERR! notarget No compatible version found: yo@'>=1.2.0-0 <1.3.0-0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0-beta.1","1.0.0-beta.2","1.0.0-beta.3","1.0.0-beta.4","1.0.0-beta.5","1.0.0-beta.6","1.0.0-beta.7","1.0.0-rc.1","1.0.0-rc.1.1","1.0.0-rc.1.2","1.0.0-rc.1.3","1.0.0-rc.1.4","1.0.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.0.7-pre.1","1.0.7-pre.2","1.0.7-pre.3","1.1.0","1.1.1","1.1.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

brew install node

In the readme you suggest installing mongo using brew.
Why not also install node using brew?

New swig templates throw an error on the home page

Currently if you create a new project using swig as your template language, using all the default options, it throws an error:

unexpected_token Error thrown for request: /
SyntaxError: Unexpected token ||
  at Object.Function (<anonymous>:null:null)
  at [object Object].precompile (/Users/Jed/Development/Tests/gen/node_modules/swig/lib/swig.js:483:11)
  at [object Object].compile (/Users/Jed/Development/Tests/gen/node_modules/swig/lib/swig.js:588:16)
  at /Users/Jed/Development/Tests/gen/node_modules/swig/lib/swig.js:666:27
  at fs.js:266:14
  at /Users/Jed/Development/Tests/gen/node_modules/keystone/node_modules/less-middleware/node_modules/less/node_modules/graceful-fs/graceful-fs.js:104:5
  at Object.oncomplete (fs.js:107:15)

@julianxhokaxhiu are you able to have a look at this?

Add an option for Coffeescript

So how about coffeescript? I'm completely addicted to it and I think coffeescript would go great with keystone. I just tried out the basics for porting in my own projected, generated using this keystone generator. keystone.js is now a simple file importing coffeescript and a setup.coffee file which contains the coffee-fied of the original setup. The server can be easily translated.

The only bit I'd be unsure about is the client-side, as we'd preferably need some pretty way to separate the coffeescript and javascript. Or is it possible to just compile all coffeescript into one big javascript file and use that for keystone? I don't know, I'm completely new to it.

Any thoughts would be appreciated or maybe cries from fellow coffeescript enthusiasts. I could attempt this option myself (New to Yeoman but that'll work out) but if someone could nudge me in the right directions that'd be great.

Cloudinary doesn't get configured properly.

Error: Invalid Configuration

CloudinaryImage fields (Gallery.heroImage) require the "cloudinary config" option to be set.

See http://keystonejs.com/docs/configuration/#cloudinary for more information.

Will submit pull request to fix

Choosing gulp as task runner breaks the generator

Looks like gulp never published (or removed) higher than 3.6.2 from the registry. The generator is expecting at least 3.6.4, which doesn't exist and subsequently fails upon attempted install.

Yeoman generator not being installed.

Ran sudo npm install -g generator-keystone, everything went well, but for some reason running yo keystone throws this error:

Error keystone 

You don't seem to have a generator with the name keystone installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 17 registered generators run yo with the `--help` option.

Tried installing using yo command's "Install a generator" option. Got same result. Not sure what am I missing at this point.

Running Ubuntu 12.04 with latest updates.

Prompt for database details

Add prompt and default for database connection details.

eg. setting from keystone-demo:

'mongo': process.env.MONGO_URI || process.env.MONGOLAB_URI || 'mongodb://localhost/keystone-demo',

I would prefer mongodb as the key name rather than mongo (and similarly, MONGODB_URI for the environment variable).

Put the new project in a subdirectory by default

It's too easy to accidentally populate an existing directory with your new project.

A better solution would be to create a new folder for the project and populate that.

Gallery Template Missing Styles

While porting the templates to HBS I was using the Jade templates as a point of reference so this is an issue in general with the layout.less

I looked at the keystone-demo itself and saw there were additional styles which result in the correct rendering once I copy/pasted them into an inline style tag.

Will submit a pull-request. Assuming I should update the layout.css file and run less and commit the minified css?

Why are users called Ys?

Just wondering if there is a reason behind it - seems like an unusual choice.

Thanks for your hard work!

Support for Sass

It would be great to have support for Sass with this generator. I know Sass is pretty popular and I think would allow developers more flexibility with styling in their pre-processor of choice. Also there's a grunt-sass plugin that works with Grunt and it's really fast.

It could be a question in the prompts, something like: Which style pre-processor would you like to include Less or Sass?

I'd be happy to add a branch for this if it's something people would like to have.

HBS Default Template Missing Pagination Functionality

Problem

During development of HBS the pagination functionality was not completed. There is a considerable amount of functionality within the pagination that must be completed.

• The actual hbs templates to create the html for the control component <ul> <li> along with previous/next buttons.
• A series of hbs helpers need to be created to aid in render the control

Can't login after generation

Yeoman generates Keystone and the database collections:

app_updates
postcategories
posts
system.indexes
users

Where users has one entry but upon trying to login. I get "Sorry, that email and password combo are not valid."

I don't know mongo shell well enough yet to see what exactly that one entry is in users, but seems the keystone generator isn't creating the initial admin user correctly.

An interesting note, I'm using crouton to launch ubuntu on a chromebook for this. Don't discriminate though it's full blown ubuntu but I don't run mongo with sudo service mongod start but instead I've only gotten the mongod command to launch a mongoDB instance. I also had to manually create mongoDB's /data/db/ directory for it.

If I could just be point to a way to add a user manually via the mongo shell I should be good. Cheers!

Hide some settings behind an "Advanced options"

Just watched a new user run through the keystone generator, and think we should hide some options (e.g. name of user model, including gulp / grunt) behind an 'advanced' option.

Prompt for details of admin user to create

Currently the initial admin user is hardcoded in 0.0.1-admins.js.

yo keystone should prompt for details, eg:

• username or email
• password
• name

For bonus points, use git user.name and user.email as defaults.

Add a registration page

Registration pages seem to be a common request, so it would be good to add one to the generator (seems a bit specific to build into keystone itself), along with forgotten password retrieval.

Can't install

getting this in terminal:
`npm ERR! peerinvalid The package yo does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.1.2
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1
npm ERR! peerinvalid Peer [email protected] wants yo@~1.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.1.2
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1.1
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.4
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1.1
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1.1
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0-rc.1
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0
npm ERR! peerinvalid Peer [email protected] wants yo@>=1.0.0

npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "generator-keystone"
npm ERR! cwd /Users/anthonybrown
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/anthonybrown/npm-debug.log
npm ERR! not ok code 0`

User signups

Hi! While playing with Keystone, how does one sign up as a Keystone user? I couldn't find the right routes or views.

Add ReactJS as Template Rendering Option

Was thinking of working on a patch to add ReactJS as a template engine.

Proposed Areas of work.

• Setup the Template Renderer for Reactjs in Express
  • Allow for ReactJS to render server-side and respond with html for SEO
• Port Default KeystoneJS Theme to ReactJS
  • Define some basic reactjs application theme layout should consist of components folder and port the html from the themes into a reactjs app. I'd probably look to port from the handlebars theme.
  • Consider making Theme isomorphic
• Build Tooling
  • Gulp + Browserify FTW!
  • Grunt (do we have to support it?)

Anyone have thoughts/comment/suggestions?

moving static resources into bower dependencies

I'm already using bower and grunt-wiredep in different projects with keystone. I
was wondering if you think that this feature will be useful to the generator i can
make a PR for that

Dynamic inclusion of preprocessor in templates

The layout file currently refers to public/styles/site.less even when the SASS preprocessor is used; it should be updated to be dynamic and based on the preprocesser chosen.

We should also include site.css instead of site.min.css when SASS is selected, it's a bit weird the way it is now.

Clean up the email templates (excl. the Jade ones)

The email templates have been ported from Jade to other languages without proper understanding of how they work, meaning they're quite broken at the moment.

The layout that the jade email templates extend is actually contained within keystone itself, not the default layout used for the site.

The markup is also a mixture of jade variables and mail chimp / mandrill variables, that are bound to the current Email implementation in Keystone.

This whole mess needs to be worked out, cleaned up, and documented.

Got exception after "yo keystone"

    Finally, would you like to include extra code comments in
    your project? If you're new to Keystone, these may be helpful. Yes
/usr/local/lib/node_modules/generator-keystone/node_modules/lodash/dist/lodash.js:6310
        throw e;
              ^
SyntaxError: Unexpected token }
    at Function (<anonymous>)
    at Function.template (/usr/local/lib/node_modules/generator-keystone/node_modules/lodash/dist/lodash.js:6305:22)
    at KeystoneGenerator.underscore [as _engine] (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/util/engines.js:31:14)
    at KeystoneGenerator.engine (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:317:10)
    at KeystoneGenerator.template (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:292:15)
    at KeystoneGenerator.project (/usr/local/lib/node_modules/generator-keystone/app/index.js:262:7)
    at /usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/base.js:387:14
    at processImmediate [as _immediateCallback] (timers.js:336:15)```

Generator Error

Tried using the recent updated generator. Got the error below. Sorry to admit it is a bit beyond me.

I ran NPM update as well as NPM -g update and no luck there (reinstalling the generator afterwards).

Any help would be much appreciated in sorting this one out

'''

/home/andrew/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:193
throw new Error('Unable to read "' + filepath + '" file (Error code: ' + e
^
Error: Unable to read "/home/andrew/local/lib/node_modules/generator-keystone/app/templates/models/_user.js" file (Error code: ENOENT).
at KeystoneGenerator.read (/home/andrew/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:193:11)
at KeystoneGenerator.template (/home/andrew/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:288:19)
at KeystoneGenerator.models (/home/andrew/local/lib/node_modules/generator-keystone/app/index.js:294:7)
at /home/andrew/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/base.js:381:14
at processImmediate as _immediateCallback

'''