You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lockit says it "comes with its own built-in views". This is sort-of correct. It is only correct if your express app uses the default view engine (jade). Lockit could actually render its own views with its own view-engine, independently of the main app. It might suffice to better document how to use your own views, and warn people that you will have to create custom views if you are not using jade as your view engine.
express --hbs --css stylus myapp
cd myapp && npm i
npm i lockit cookie-session
edit app.js to include
var cookieSession = require('cookie-session');
var Lockit = require('lockit');
var lockit = new Lockit();
...
app.use(cookieSession({secret: 'my super secret String'}));
app.use(lockit.router);
Visit localhost:3000/login
ERROR Failed to lookup view "/Users/dhall/projects/myapp/node_modules/lockit/node_modules/lockit-login/views/get-login" in views directory "/Users/dhall/projects/myapp/views"
The text was updated successfully, but these errors were encountered:
Lockit says it "comes with its own built-in views". This is sort-of correct. It is only correct if your express app uses the default view engine (jade). Lockit could actually render its own views with its own view-engine, independently of the main app. It might suffice to better document how to use your own views, and warn people that you will have to create custom views if you are not using jade as your view engine.
edit app.js to include
Visit localhost:3000/login
ERROR
Failed to lookup view "/Users/dhall/projects/myapp/node_modules/lockit/node_modules/lockit-login/views/get-login" in views directory "/Users/dhall/projects/myapp/views"
The text was updated successfully, but these errors were encountered: