Detailed explanation of webpack packaged koa2 framework app examples
When I used koa to write servers, publishing was a nightmare. All files in src need to be overwritten, and the config configuration file must also be overwritten. If you are not careful, various problems will be reported online, and then you have to roll back and adjust them locally before publishing. I accidentally saw an article about how to use webpack to package koa app. I was shocked. It turns out that webpack can also package the backend. I had never thought of this before. This article mainly introduces to you the steps and final deployment of using webpack to package the koa2 framework. It is very practical. Friends in need can refer to it. I hope it can help you.
Key issues
1: All modules in node_modules are not packaged
The core functions of webpack It is to type each referenced module into a file, and unified modularization of various standardized modules (webpack specification).
However, node contains a large number of fs and path operations. These fs and path operations will have no operation objects after the packaging is completed, and many various errors will be reported.
So the core of using webpack for packaging is to refuse to package all modules in node_modules, and only package the files referenced by relative paths into one file. It happened that we found that webapck provides the externals attribute to exclude modules that do not need to be packaged.
If we dig deeper, we can find that modules like webpack, nodemon, and babel-preset-env are packages that the app development environment depends on, and our program will not require these modules at all.
In summary, we can find that: we only need to exclude all required packages. This module corresponds to the module under dependencies in package.json. It is important to understand the difference between dependencies and devDependencies.
So we can use the externals-dependencies plug-in with the externals attribute to exclude dependencies.
Code:
1 2 3 4 5 6 7 |
|
2: target points to node
Official document: Compiled to class Node.js The environment is available (use Node.js require to load chunk)
Code:
target: 'node',
3: Add node configuration
Official documentation: These options can configure whether to polyfill or mock certain Node.js global variables and modules. This allows code originally written for the Node.js environment to run in other environments such as browsers.
Code:
node: {
console: true,
global: true,
process: true,
Buffer: true,
__filename: true,
__dirname: true,
setImmediate: true,
path: true
},
##Four: babel configuration
In order to be compatible with lower versions of node, async/await is not natively supported. Here I use babel-preset-env{"modules": false} configuration for babel. This configuration will convert es6 syntax to es5 syntax, such as let and const to var. At the same time, all async/await functions are also converted into the _asyncToGenerator function defined in the polyfill.function _asyncToGenerator(fn) { return function () { var gen = fn.apply(this, arguments); return new Promise(function (resolve, reject) { function step(key, arg) { try { var info = gen[key](arg); var value = info.value; } catch (error) { reject(error); return; } if (info.done) { resolve(value); } else { return Promise.resolve(value).then(function (value) { step("next", value); }, function (err) { step("throw", err); }); } } return step("next "); }); }; }In fact, promises are used to implement the functions of async functions. Of course this function also requires the regeneratorRuntime function when running. So I introduced babel-polyfill globally to provide the regeneratorRuntime function. Note: If your node version is very high and supports async/await natively, you can omit babel-preset-env and babel-polyfillCode:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 |
|
Deployment
After packaging, deployment is much more convenient. You only need to add package.json, app.js, and html in the view Just deploy and go online. Then execute1. npm installon the server and then the server will run in the background. If you need to update and publish, you only need to re-package npm run dev or npm run build locally and drag it to the server to overwrite app.js. Related recommendations:2. npm run for
10 recommended articles about koa2
Sharing example tutorials on using the koa2 framework in nodejs
Tutorial on using koa2 framework in nodejs6
The above is the detailed content of Detailed explanation of webpack packaged koa2 framework app examples. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Vue is an excellent JavaScript framework that can help us quickly build interactive and efficient web applications. Vue3 is the latest version of Vue, which introduces many new features and functionality. Webpack is currently one of the most popular JavaScript module packagers and build tools, which can help us manage various resources in our projects. This article will introduce how to use Webpack to package and build Vue3 applications. 1. Install Webpack

Introduction to Caddy Caddy is a powerful and highly scalable web server that currently has 38K+ stars on Github. Caddy is written in Go language and can be used for static resource hosting and reverse proxy. Caddy has the following main features: Compared with the complex configuration of Nginx, its original Caddyfile configuration is very simple; it can dynamically modify the configuration through the AdminAPI it provides; it supports automated HTTPS configuration by default, and can automatically apply for HTTPS certificates and configure it; it can be expanded to data Tens of thousands of sites; can be executed anywhere with no additional dependencies; written in Go language, memory safety is more guaranteed. First of all, we install it directly in CentO

Form validation is a very important link in web application development. It can check the validity of the data before submitting the form data to avoid security vulnerabilities and data errors in the application. Form validation for web applications can be easily implemented using Golang. This article will introduce how to use Golang to implement form validation for web applications. 1. Basic elements of form validation Before introducing how to implement form validation, we need to know what the basic elements of form validation are. Form elements: form elements are

Using Jetty7 for Web Server Processing in JavaAPI Development With the development of the Internet, the Web server has become the core part of application development and is also the focus of many enterprises. In order to meet the growing business needs, many developers choose to use Jetty for web server development, and its flexibility and scalability are widely recognized. This article will introduce how to use Jetty7 in JavaAPI development for We

First of all, you will have a doubt, what is frp? Simply put, frp is an intranet penetration tool. After configuring the client, you can access the intranet through the server. Now my server has used nginx as the website, and there is only one port 80. So what should I do if the FRP server also wants to use port 80? After querying, this can be achieved by using nginx's reverse proxy. To add: frps is the server, frpc is the client. Step 1: Modify the nginx.conf configuration file in the server and add the following parameters to http{} in nginx.conf, server{listen80

Face-blocking barrage means that a large number of barrages float by without blocking the person in the video, making it look like they are floating from behind the person. Machine learning has been popular for several years, but many people don’t know that these capabilities can also be run in browsers. This article introduces the practical optimization process in video barrages. At the end of the article, it lists some applicable scenarios for this solution, hoping to open it up. Some ideas. mediapipeDemo (https://google.github.io/mediapipe/) demonstrates the mainstream implementation principle of face-blocking barrage on-demand up upload. The server background calculation extracts the portrait area in the video screen, and converts it into svg storage while the client plays the video. Download svg from the server and combine it with barrage, portrait

Web standards are a set of specifications and guidelines developed by W3C and other related organizations. It includes standardization of HTML, CSS, JavaScript, DOM, Web accessibility and performance optimization. By following these standards, the compatibility of pages can be improved. , accessibility, maintainability and performance. The goal of web standards is to enable web content to be displayed and interacted consistently on different platforms, browsers and devices, providing better user experience and development efficiency.

Cockpit is a web-based graphical interface for Linux servers. It is mainly intended to make managing Linux servers easier for new/expert users. In this article, we will discuss Cockpit access modes and how to switch administrative access to Cockpit from CockpitWebUI. Content Topics: Cockpit Entry Modes Finding the Current Cockpit Access Mode Enable Administrative Access for Cockpit from CockpitWebUI Disabling Administrative Access for Cockpit from CockpitWebUI Conclusion Cockpit Entry Modes The cockpit has two access modes: Restricted Access: This is the default for the cockpit access mode. In this access mode you cannot access the web user from the cockpit
