Error No default engine was specified and no extension was provided

Question

I am working through setting up a http server using node js and engine  However  I keep running into issues that I have little information on how to resolve I would appreciate some help solving  this please    Error  No default engine was specified and no extension was provided   at new View      node modules express lib view js 41 42   at Function app render      node modules express lib application js 484 12   at ServerResponse res render      node modules express lib response js 783 7   at Layer handle      app js 123 7   at trim prefix      node modules express lib router index js 225 17   at c      node modules express lib router index js 198 9   at Function proto process params      node modules express lib router index js 253 12   at next      node modules express lib router index js 189 19   at next      node modules express lib router index js 202 7   at next      node modules express lib router index js 166 38    Below is what I have set up to start up this engine    var http   require  http      var module   require  module   var logger   require  morgan    var express   require  express    var app    module exports   express    var silent    test     process env NODE ENV  var httpServer   http createServer app       app middleware  app enable  strict routing       app all      function req  res  next      CORS support              if   req get  Origin    return next      use     here to accept any origin      res set  Access-Control-Allow-Origin    http   localhost 3000         res set  Access-Control-Allow-Methods    GET  POST         res set  Access-Control-Allow-Headers    X-Requested-With  Content-Type         res set  Access-Control-Allow-Max-Age   3600        if   OPTIONS     req method  return res send 200        next           app set  views     dirname     views       general config app set  view engine    html    app get   404   function req  res  next   next      trigger a 404 since no other middleware will match  404 after this one  and we re not responding here     app get   403   function req  res  next     trigger a 403 error   var err   new Error  not allowed       err status   403    next err       app get   500   function req  res  next     trigger a generic  500  error   next new Error  keyboard cat          app use express static   dirname     public        error handlers app use logErrors   app use clientErrorHandler   app use errorHandler        middleware with an arity of 4 are considered error handling middleware  When you next err     it will be passed through the defined middleware in order  but ONLY those with an arity of 4  ignoring regular middleware  function clientErrorHandler err  req  res  next      if  req xhr      whatever you want here  feel free to populate properties on  err  to treat it differently in here    res send err status    500    error  err message            else      next err          create an error with  status  we can then use the property in our custom error handler  Connect repects this prop as well  function error   status  msg      var err   new Error msg     err status   status    return err     function logErrors   err  req  res  next      console error err stack     next err      function errorHandler  err  req  res  next      res status 500     res render  error     error  err            Error handlers    Since this is the last non-error-handling middleware use  d  we assume 404  as nothing else responded       curl http   localhost 3000 notfound      curl http   localhost 3000 notfound -H  Accept  application json       curl http   localhost 3000 notfound -H  Accept  text plain  app use function req  res  next     res status 404      if  req accepts  html        respond with html page     res render  404     url  req url         return         if  req accepts  json        respond with json     res send   error   Not found          return         res type  txt   send  Not found      default to plain-text  send           error-handling middleware  take the same form as regular middleware  however they require an    arity of 4  aka the signature  err  req  res  next  when connect has an error  it will invoke ONLY error-handling middleware      If we were to next   here any remaining non-error-handling middleware would then be executed  or if we next err  to    continue passing the error  only error-handling middleware would remain being executed  however here    we simply respond with an error page  app use function err  req  res  next        we may use properties of the error object here and next err  appropriately  or if we possibly recovered from the error  simply next      res status err status    500     res render  500     error  err          if   module parent      assigning to exports will not modify module  must use module exports   app listen 3000     silent    console log  Express started on port 3000

User · Answer

The res render stuff will throw an error if you re not using a view engine    If you just want to serve json replace the res render  error     error  err     lines in your code with   res json   error  err      PS  People usually also have message in the returned object   res status err status    500   res json     message  err message    error  err

User · Answer

If all that s needed is to send html code inline in the code  we can use below  var app   express    app get   test html   function  req  res       res header  Content-Type    text html   send   lt html gt my html code lt  html gt

User · Answer

if you ve got this error by using the express generator  I ve solved it by using express --view ejs myapp  instead of express --view pug myapp

User · Answer

I just got this error message  and the problem was that I was not setting up my middleware properly   I am building a blog in the MEAN stack and needed body parsing for the  jade files that I was using on the front end side  Here is the snippet of code from my   middleware index js  file  from my project   var express   require  express    var morgan   require  morgan    var session   require  express-session    var cookieParser   require  cookie-parser    var bodyParser   require  body-parser     module exports   function  app    app use morgan  dev         Good for now    In the future  use connect-mongo or similar    for persistant sessions app use bodyParser json     app use bodyParser urlencoded       extended  true      app use cookieParser     app use session  secret   building a blog   saveUninitialized  true  resave  true       Also  here is my  package json  file  you may be using different versions of technologies  Note  because I am not sure of the dependencies between them  I am including the whole file here    dependencies          body-parser    1 12 3        consolidate    0 12 1        cookie-parser    1 3 4        crypto    0 0 3        debug    2 1 1        express    4 12 2        express-mongoose    0 1 0        express-session    1 11 1        jade    1 9 2        method-override    2 3 2        mongodb    2 0 28        mongoose    4 0 2        morgan    1 5 1        request    2 55 0        serve-favicon    2 2 0        swig    1 4 2        Hope this helps someone  All the best

User · Answer

Error  No default engine was specified and no extension was provided   I got the same problem for doing a mean stack project   the problem is i didn t mentioned the formate to install npm i e  pug or jade ejs etc  so to solve this goto npm and enter express --view pug foldername  This will load necessary pug files index pug layout pug etc    in ur given folder

User · Answer

Comment out the res render lines in your code and add in next err   instead  If you re not using a view engine  the res render stuff will throw an error   Sorry  you ll have to comment out this line as well   app set  view engine    html      My solution would result in not using a view engine though  You don t need a view engine  but if that s the goal  try this   app set  views   path join   dirname   views     app set  view engine    jade      swap jade for ejs etc   You ll need the res render lines when using a view engine as well  Something like this      error handlers    development error handler    will print stacktrace if  app get  env        development       app use function err  req  res  next        res status err status    500       res render  error         message  err message      error  err                    production error handler    no stacktraces leaked to user app use function err  req  res  next      res status err status    500     next err     res render  error       message  err message    error

User · Answer

Just set view engine in your code   var app   express     app set  view engine    ejs

User · Answer

Please replace app set  view engin    html      with app set  view engine    ejs

User · Answer

You can use express-error-handler to use static html pages for error handling and to avoid defining a view handler   The error was probably caused by a 404  maybe a missing favicon  apparent if you had included the previous console message   The  view handler  of  html  doesn t seem to be valid in 4 x express   Regardless of the cause  you can avoid defining a  valid  view handler as long as you modify additional elements of your configuration   Your options are to fix this problem are    Define a valid view handler as in other answers Use send   instead of render to return the content directly   http   expressjs com en api html res render  Using render without a filepath automatically invokes a view handler as with the following two lines from your configuration   res render  404     url  req url       and   res render  500     Make sure you install express-error-handler with   npm install --save express-error-handler   Then import it in your app js  var ErrorHandler   require  express-error-handler      Then change your error handling to use      define below all other routes var errorHandler   ErrorHandler     static         404    error html     put this file in your Public folder      500    error html     ditto         any unresolved requests will 404 app use function req res next      var err   new Error  Not Found      err status 404     next err      app use errorHandler

User · Answer

The above answers are correct  but I found that a simple typo can also generate this error  For example  I had var router   express   instead of var router   express Router   and got this error  So it should be the following       App js  var express   require  express    var app   express    var bodyParser   require  body-parser    app use bodyParser urlencoded   extended false        assuming you put views folder in the same directory as app js app set  views     dirname     views   app engine  ejs   ejs renderFile   app set  view engine    ejs       router - wherever you put it  could be in app js var router   express Router    router get      function  req res      res render   index ejs

User · Answer

instead of app get       req  res    gt  res render  Hellooooo     use app get       req  res    gt  res send  Hellooooo

User · Answer

You are missing the view engine  for example use jade   change your   app set  view engine    html      with  app set  view engine    jade      If you want use a html friendly syntax use instead ejs  app engine  html   require  ejs   renderFile   app set  view engine    html      EDIT  As you can read from view js Express View Module   module exports   View          Initialize a new  View  with the given  name         Options          -  defaultEngine  the default template engine name      -  engines  template engine require   cache      -  root  root path for view lookup        param  String  name     param  Object  options     api private      function View name  options      options   options          this name   name    this root   options root    var engines   options engines    this defaultEngine   options defaultEngine    var ext   this ext   extname name     if   ext  amp  amp   this defaultEngine  throw new Error  No default engine was specified and no extension was provided       if   ext  name     ext   this ext           this defaultEngine 0                this defaultEngine     this engine   engines ext      engines ext    require ext slice 1     express     this path   this lookup name       You must have installed a default engine   Express search default layout view by program template as you can read below   mkdir path     views   function          switch  program template            case  ejs             write path     views index ejs   ejsIndex             break          case  jade             write path     views layout jade   jadeLayout             write path     views index jade   jadeIndex             break          case  jshtml             write path     views layout jshtml   jshtmlLayout             write path     views index jshtml   jshtmlIndex             break          case  hjs             write path     views index hjs   hoganIndex             break                     and as you can read below   program template    jade   if  program ejs  program template    ejs   if  program jshtml  program template    jshtml   if  program hogan  program template    hjs     the default view engine is jade

User · Answer

If you wish to render a html file  use  response sendfile  index html     Then you remove  app set  view engine    html     Put your   html in the views directory  or serve a public directory as static dir and put the index html in the public dir

User · Answer

set view engine following way   app set  views   path join   dirname   views     app set  view engine    jade

[node.js] Error: No default engine was specified and no extension was provided

Examples related to node.js

Examples related to http

Examples related to express