Let’s install Nodejs and other dependencies we need in the project, once it is done running it adds node modules folder and package-lock.json file: Every dependency you add in this project will show in the package.json file. You have successfully created a package.json file, located in the root folder of your project, for project identification and contain dependencies we will install add.
package name: (newproject) version: (1.0.0) description: entry point: (index.js) app.js test command: git repository: keywords: author: license: (ISC) The dependencies However you can specify all the fields, read more about the content of the package.json fields here to make informed changes. By running the code below, we initiate our project by creating a package.json file.Īs shown below, I did not change anything except entry point, I changed from index.js (default) to app.js. I recommend using the terminal in vsCode because it is easier to access, you do not need to enter the path directory. Open the folder newProject in Visual Studio Code (VSCode). Use the IDE of your choice, in my case I am using Visual Studio Code. Start by creating a folder in a directory of your choice using the terminal. In addition to the prerequisite mentioned above, you must be familiar with JavaScript. Click here to get Nodejs if you do not have one. To get hands on experience with this article you need to have: At the end of this tutorial, you would have created an single web page and learn how to use the technologies mentioned above. We will create a Node application from scratch, set up Nodejs, express, and a pug template engine. In this tutorial, I will explain how to use a pug template and NodeJS to build a web page. Pug is simply too alien from native HTML and resembles a lot more like those other off-side rule languages like Python.Image by Free-Photos from Pixabay Introduction
Pug templates are nice for Python programmers who don't want to learn HTML to start writing web pages and develop some entire websites personally from the ground up, but for any serious project that involves more than half a dozen people and has separate positions of web UI designers, front-end developers, and back-end engineers, it's much better to choose something more closely compatible with native HTML as the template engine.
Plain HTML pages usually can contain very deeply nested structures, whether they are hand-written by web UI designers or generated from popular web design tools or taken from existing HTML templates, which are a nightmare for front-end engineers to convert into Pug templates, where you have to take care of handling the indentation rules and the deeply nested HTML elements, even creating multiple blocks that don't have any meaning in terms of business logic, just to house the HTML elements within bearable amounts of indentations.
0 kommentar(er)
