Some common problems with Nuxt.js (detailed tutorial)

This article mainly introduces the summary and sharing of Nuxt.js pitfalls. Now I share it with you and give you a reference.

Building issues

1. How to introduce js files in the head?

Background: In the 93f0f5c25f18dab9d176bd4f6de5d30e tag , introduce the flexible.js file in inline form. This project is mainly a mobile terminal project, and flexible.js is introduced to realize mobile terminal adaptation issues.
Nuxt.js implements header tag management through vue-meta. By viewing the document, we found that it can be configured as follows:

// nuxt.config.js
head: {
 script: [
  { innerHTML: 'console.log("hello")', type: 'text/javascript', charset: 'utf-8'}
 ]
}

As a result, html is generated:

<script data-n-head="true" type="text/javascript" charset="utf-8">console.log("hello")</script>

We found that vue- meta has escaped the quotation marks. After adding __dangerouslyDisableSanitizers: ['script'], these characters will no longer be escaped. Use this field with caution!

Next, replace the content of console.log("hello") with flexible.js. After the configuration is upgraded:

head: {
 script: [{ innerHTML: require('./assets/js/flexible'), type: 'text/javascript', charset: 'utf-8'}],
 __dangerouslyDisableSanitizers: ['script']
}

Successfully stepped into the pit, the next pit...

2. How to use preprocessors

Background: Use various preprocessors on d477f9ce7bf77f53fbcf36bec1b69b7a, 3f1c4e4b6b16bbbd69b2ee476dc4f83a or c9ccee2e6ea535a969eb3f532ad9fe89 in components , after adding the processor, the console reports an error.

<style lang="sass">
.red
 color: red
</style>

The solution to this problem is very simple, just install these dependencies.

npm install --save-dev node-sass sass-loader

But the solution process was not very smooth. When reading the Chinese document, I ignored the version number and followed the above prompts. I found that it could not succeed. After various debugging, I finally found the solution. I later discovered that the version number of the Chinese document was too low. If you need to view the document, be sure to read the latest version of the English document!

3. How to use px2rem

Background: In css, write px, and convert px to rem through px2rem loader

In the past In the project, it is implemented through px2rem loader, but in the Nuxt.js project, adding css loader is still very laborious because vue-loader is involved.

I thought of another solution, which can be processed using postcss. Configuration can be added in the nuxt.config.js file or in the postcss.conf.js file.

build: {
 postcss: [
  require('postcss-px2rem')({
   remUnit: 75 // 转换基本单位
  })
 ]
},

4. How to expand webpack configuration

Background: Add an alias to the utils directory

As I just mentioned, Nuxt.js has built-in webpack configuration. If you want to expand the configuration, you can add it in the nuxt.config.js file. At the same time, you can also print out the configuration information in this file.

extend (config, ctx) {
 console.log('webpack config:', config)
 if (ctx.isClient) {
  // 添加 alias 配置
  Object.assign(config.resolve.alias, {
   'utils': path.resolve(__dirname, 'utils')
  })
 }
}

5. How to add vue plugin

Background: I have encapsulated a toast vue plugin. Since the vue instantiation process is not exposed, I don’t know at what time. Inject it.

You can add the plugins configuration in nuxt.config.js so that the plugins will be loaded and imported before the Nuxt.js application is initialized.

module.exports = {
 plugins: ['~plugins/toast']
}

~plugins/toast.js file:

import Vue from 'vue'
import toast from '../utils/toast'
import '../assets/css/toast.css'

Vue.use(toast)

6. How to modify the environment variable NODE_ENV

Background: In the project, set three NODE_ENV values ​​to correspond different versions. development, local development; release, pre-release version; production, online version. Among them, the pre-release version has more vconsole than the production version.

// package.json
"scripts": {
 "buildDev": "cross-env NODE_ENV=release nuxt build && backpack build",
 "startDev": "cross-env NODE_ENV=release PORT=3000 node build/main.js"
 },

Print process.env.NODE_ENV is still production.

I found the answer in the backpack source code. When executing the backpack build command, process.env.NODE_ENV will be modified to production, and it is hard-coded and non-configurable...

With no choice, we can only add the __ENV attribute under process.env, which represents NODE_ENV

At this time, the information printed on the page process.env .__ENV is undefined, but process.env.NODE_ENV can be printed out.

This problem can be solved by configuring the env attribute in nuxt.config.js.

env: {
 __ENV: process.env.__ENV
}

Development issues

1. Window or Document object is not defined?

Background: When introducing third-party plug-ins or writing window directly in the code, the console will give a warning that window is undefined.
When this problem occurs, the node server does not have a window or document object. The solution is to use process.browser to distinguish the environment.

if (process.browser) {
 // 引入第三方插件
 require('***')
 // 或者修改window对象下某一属性
 window.mbk = {}
}

The above is what I compiled for everyone. I hope it will be helpful to everyone in the future.

Related articles:

Using AnglarJs to implement pull-up loading

How to implement the selected change method using vue.js

How to prevent click events from bubbling in vue

Vue.js Click a button to show/hide content

How to change the display and hiding of the current item in vue

Ionic implements verification code countdown

How to implement the parent component click to trigger the child component in vue event

The above is the detailed content of Some common problems with Nuxt.js (detailed tutorial). For more information, please follow other related articles on the PHP Chinese website!