express-generator no-view

1 of 7

Try running this command in command prompt:

express --help

It will give you the express generator help:

  Usage: express [options] [dir]

  Options:

    -h, --help          output usage information
        --version       output the version number
    -e, --ejs           add ejs engine support
        --hbs           add handlebars engine support
        --pug           add pug engine support
    -H, --hogan         add hogan.js engine support
        --no-view       generate without view engine
    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
        --git           add .gitignore
    -f, --force         force on non-empty directory

^{Source: https://expressjs.com/en/starter/generator.html}

The above options give you the list of "view engines".

Now, simply type:

express -{your choice view engine}

For example using `express -e`:

This sets the EJS engine as your view handler and removes jade. EJS has the look and feel of HTML with the added ability to inject values via their template system.

2 of 7

If you won't a view engine just type:

express --no-view

You can add an engine after or not working with server rendering.

Videos

13:36

Express JS Tutorial #13 - Express Generator | Expressjs Tutorial ...

October 19, 2020

15:20

Setting up Express with Express-generator - YouTube

May 29, 2019

06:25

NodeJS Essentials 22: Express Generator - YouTube

June 11, 2019

09:31

Node JS Express Generator | Express Generator Node JS Tutorial ...

February 5, 2018

View all

npm

npmjs.com › package › express-generator

express-generator - npm

The quickest way to get started with express is to utilize the executable express(1) to generate an application as shown below: ... This generator can also be further configured with the following command line flags. --version output the version number -e, --ejs add ejs engine support --pug add pug engine support --hbs add handlebars engine support -H, --hogan add hogan.js engine support -v, --view <engine> add view <engine> support (dust|ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade) --no-view use static html instead of view engine -c, --css <engine> add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css) --git add .gitignore -f, --force force on non-empty directory -h, --help output usage information

      » npm install express-generator

Published May 03, 2019

Version 4.16.1

Author TJ Holowaychuk

Repository https://github.com/expressjs/generator

Homepage https://github.com/expressjs/generator#readme

github.com › expressjs › generator

GitHub - expressjs/generator: Express' application generator

You can also run the application generator with the npx command (available since Node.js 8.2.0). ... The quickest way to get started with express is to utilize the executable express(1) to generate an application as shown below: ... This generator can also be further configured with the following command line flags. --version output the version number -e, --ejs add ejs engine support --pug add pug engine support --hbs add handlebars engine support -H, --hogan add hogan.js engine support -v, --view <engine> add view <engine> support (dust|ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade) --no-view use static html instead of view engine -c, --css <engine> add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css) --git add .gitignore -f, --force force on non-empty directory -h, --help output usage information

Starred by 1.9K users

Forked by 552 users

github.com › expressjs › generator › issues › 152

Option for no view engine · Issue #152 · expressjs/generator

With the wealth of front end frameworks available now, I don't find it appealing to use any of the view engines, though bootstrapping technologies like this project appeal to me. My use case is as follows: Angular front end transpiled/compiled/obfuscated/minified/whatever into a bunch of static blobs · Nginx delivering the client (bunch of static blobs) Express ...

Stack Overflow

stackoverflow.com › questions › 14681276 › how-to-make-an-express-site-without-a-template-engine

How to make an Express site without a template engine? - Stack Overflow

youtrack.jetbrains.com › issue › WEB-32067 › node-express-generator-Support-new-no-view-option-for-node-express-generator

1 of 7

If what you want is directly to serve static html files with the possibility to cache resources, while still being able to hit "/" and get index.html, then the answer is as easy as this:

var express = require('express');
var http = require('http');
var app = express();

app.use(express.static(__dirname + '/public'));

http.createServer(app).listen(3000);

Gotcha: Html files including index.html must be inside /public folder instead of /views

2 of 7

You could use commands below to install express-generator globally and then scaffold a project without a view engine

 npm install -g express-generator
 express newProject --no-view

JetBrains

Support new '--no-view' option for node express-generator

{{ (>_<) }} This version of your browser is not supported. Try upgrading to the latest stable version. Something went seriously wrong

Medium

medium.com › @ABiasedHypocrite › simplest-and-fastest-react-express-app-setup-8497ed8db0d1

Simplest and Fastest React Express App Setup | by Jorge Fuentes | Medium

December 11, 2021 - Express generator is a similar tool maintained by the creators of Express. It usually comes with its own jade or ejs frontend, but this can be avoided with the --no-view flag.

Find elsewhere

Google Bing Mojeek

MDN Web Docs

developer.mozilla.org › en-US › docs › Learn › Server-side › Express_Nodejs › skeleton_website

Express Tutorial Part 2: Creating a skeleton website - Learn web ...

Note: The other options for choosing template engines (e.g., --hogan, --ejs, --hbs etc.) are deprecated. Use --view (or -v). The Express Application Generator allows you to configure a number of popular view/templating engines, including EJS, Hbs, Pug (Jade), Twig, and Vash, although it chooses Jade by default if you don't specify a view option.

github.com › donnybrilliant › express-generator

GitHub - donnybrilliant/express-generator: Express' application generator

Author donnybrilliant

reddit.com › r › node › comments › iq9v2l › express_generator_difference_between_e_and_v

r/node - Express Generator difference between -e and -v options?!

May 17, 2017 -

Hi all. I am certain this is a stupid question.. apologies in advance.

Express help contains the following:

> express --help

    Usage: express [options] [dir]


  Options:

        --version        output the version number
    -e, --ejs            add ejs engine support
        --pug            add pug engine support
        --hbs            add handlebars engine support
    -H, --hogan          add hogan.js engine support
    -v, --view <engine>  add view <engine> support (dust|ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
        --no-view        use static html instead of view engine
    -c, --css <engine>   add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
        --git            add .gitignore
    -f, --force          force on non-empty directory
    -h, --help           output usage information

My question is, what is the difference between the -e option and the -v option? I've been searching for days and I simply cannot find a clear answer to this. Please, somebody, explain and help put me out of my misery !

1 of 2

My wild guess is that '-e' does what it says, It adds ejs as view engine, maybe because its the most popular so you dont have to write '-v ejs' .. but im purely guessing now based on the manual you provided.

2 of 2

-1

I would focus on --no-view, that's where the magic is...

github.com › seanpmaxwell › express-generator-typescript

GitHub - seanpmaxwell/express-generator-typescript: Create a new express app similar to express-generator but with TypeScript

There are some other tools out ... a lot of junk in your project (such as an ORM). Due to the heavy use of single-page-applications, no view-engine is configured by default....

Starred by 937 users

Forked by 87 users

Languages TypeScript 77.1% | JavaScript 15.8% | HTML 5.8% | CSS 1.3%

Stack Overflow

stackoverflow.com › questions › 47948325 › using-node-js-express-without-template-engine

Using Node.js + Express without template engine

1 of 2

Passing this as the answer

Try res.sendFile(path.join(__dirname + '/../public/index.html'))

2 of 2

If you're starting from scratch, you can run:

npm install -g express-generator # to install express-generator globally
express projectName --no-view --git # '--git' is optional and generates a '.gitignore' file

github.com › luiztools › express-generator

GitHub - luiztools/express-generator: Express' application generator

The quickest way to get started ... command line flags. --version output the version number --no-view use static html instead of view engine -f, --force force on non-empty directory -h, --help output usage infor...

Starred by 8 users

Forked by 5 users

Languages JavaScript 94.3% | EJS 4.9%

npm

npmjs.com › package › express-generator-typescript

express-generator-typescript - npm

There are some other tools out ... a lot of junk in your project (such as an ORM). Due to the heavy use of single-page-applications, no view-engine is configured by default....

      » npm install express-generator-typescript

Published Nov 10, 2025

Version 2.7.4

Author sean maxwell

Repository https://github.com/seanpmaxwell/express-generator-typescript

Homepage https://github.com/seanpmaxwell/express-generator-typescript#readme

SitePoint

sitepoint.com › blog › javascript › create new express.js apps in minutes with express generator

Create New Express.js Apps in Minutes with Express Generator

November 13, 2024 - To use express-generator, Node and npm must be installed. The tool is installed as a global package using the command ‘npm install express-generator -g’, and a new Express project is created with the command ‘express myapp’. The generated Express application begins with four folders: ‘bin’ (contains the executable file that starts the app), ‘public’ (stores JavaScript, CSS, images, and other assets), ‘routes’ (contains router files), and ‘views’ (contains files used by the templating engine).

SAP

developers.sap.com › tutorials › basic-nodejs-application-create.html

Create a Basic Node.js Application with Express Generator | SAP Tutorials

Package express is installed together. Verify if you have successfully installed the tool: ... . ├── app.js ├── bin │ └── www ├── package.json ├── public │ ├── images │ ├── javascripts │ └── stylesheets │ └── style.css ├── routes │ ├── index.js │ └── users.js └── views ├── error.jade ├── index.jade └── layout.jade 7 directories, 9 files

reddit.com › r/node › trouble setting js as express view engine

r/node on Reddit: trouble setting js as express view engine

January 1, 2024 -

Hi,

I am learning express but I don't want to use ejs, pug or JSX as view engine.

Since javaScript provides string template, I want to use it.

I use the express-generator template.

/view/index.js

`<h1>${title}</h1>`
`<p> Welcome to ${title}</p>`

/app.js

var indexRouter = require('./routes/index');
...
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'js');
...
app.use('/', indexRouter);

/routes/index.js

var express = require('express');
var router = express.Router();

/* GET home page. */
router.get('/', function(req, res, next) {
  res.render('index', { title: 'Express' });
});

module.exports = router;

However when I node ./bin/www I get this error message:

Error: Cannot find module 'js'
Require stack:
- /home/capeya/localLibrary/node_modules/express/lib/view.js
- /home/capeya/localLibrary/node_modules/express/lib/application.js
- /home/capeya/localLibrary/node_modules/express/lib/express.js
- /home/capeya/localLibrary/node_modules/express/index.js
- /home/capeya/localLibrary/app.js
- /home/capeya/localLibrary/bin/www
    at Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
    at Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at new View (/home/capeya/localLibrary/node_modules/express/lib/view.js:81:14)
    at Function.render (/home/capeya/localLibrary/node_modules/express/lib/application.js:587:12)
    at ServerResponse.render (/home/capeya/localLibrary/node_modules/express/lib/response.js:1039:7)
    at /home/capeya/localLibrary/app.js:38:7
    at Layer.handle_error (/home/capeya/localLibrary/node_modules/express/lib/router/layer.js:71:5)
    at trim_prefix (/home/capeya/localLibrary/node_modules/express/lib/router/index.js:326:13)

Tried to look for a solution online but I found nothing about setting javascript files as view engine in express.

When I remove app.set('view engine', 'js'); then I get

Error: No default engine was specified and no extension was provided.