Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Error when using yeoman to generate angular app: unhandled Template render error

I want to use yeoman to generate an angular app structure, but an error stopped me.

yo-->Angular Bootstrap-->more options-->

error occurs:

Possibly unhandled Template render error: (unknown path) [Line 3, Column 90]
  expected variable end
    at Object.exports.withPrettyErrors (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/nunjucks/src/lib.js:33:17)
    at Obj.extend.render (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/nunjucks/src/environment.js:344:20)
    at Obj.extend.renderString (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/nunjucks/src/environment.js:231:21)
    at Generator.engine [as _engine] (/usr/lib/node_modules/generator-angular-bootstrap/app/modules/nunjucks-engine.js:17:14)
    at Generator.engine (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/yeoman-generator/lib/actions/actions.js:314:10)
    at Generator.template (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/yeoman-generator/lib/actions/actions.js:289:15)
    at setupAppFiles (/usr/lib/node_modules/generator-angular-bootstrap/app/index.js:209:10)
    at tryCatch1 (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/bluebird/js/main/util.js:45:21)
    at Promise$_callHandler [as _callHandler] (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/bluebird/js/main/promise.js:658:13)
    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/usr/lib/node_modules/generator-angular-bootstrap/node_modules/bluebird/js/main/promise.js:672:18)

So, anyone can help me?

like image 794
creeper Avatar asked Oct 27 '14 02:10

creeper


1 Answers

I've "solved" by downgrading the version from 0.5.1 to 0.4.3:

$ sudo npm uninstall -g generator-angular-bootstrap
$ sudo npm install -g [email protected]
$ yo angular-bootstrap

This error seems to be related to nunjucks -- which was introduced in version 0.5.0 (I've experienced the error in 0.5.0 and 0.5.1); and probably related to something else I couldn't identify quickly.

like image 111
thicolares Avatar answered Oct 14 '22 00:10

thicolares