# FAQ
# General
# Can it be used in a production environment?
Umi is the underlying front-end framework of Ant Financial, which has directly or indirectly served 600+ applications, including java, node, H5 wireless, Hybrid applications, pure front-end assets applications, CMS applications, and more.
# How do I view the version numbers such as react, react-dom, and react-router?
$ umi -v --verbose
umi@2.0.0
darwin x64
node@v10.6.0
umi-build-dev@1.0.0
af-webpack@1.0.0
babel-preset-umi@1.0.0
umi-test@1.0.0
react@16.4.2 (/Users/chencheng/code/github.com/ant-design/ant-design-pro/node_modules/react)
react-dom@16.4.2 (/Users/chencheng/code/github.com/ant-design/ant-design-pro/node_modules/react-dom)
react-router@4.3.1 (/Users/chencheng/code/github.com/umijs/umi/packages/umi-build-dev/node_modules/react-router)
react-router-dom@4.3.1 (/Users/chencheng/code/github.com/ant-design/ant-design-pro/node_modules/react-router-dom)
dva@2.4.0 (/Users/chencheng/code/github.com/ant-design/ant-design-pro/node_modules/dva)
dva-loading@2.0.5
dva-immer@0.2.3
path-to-regexp@1.7.0
# How to introduce @babel/polyfill?
Install dependencies first,
$ yarn add @babel/polyfill
Then create a new src/global.js
with the following contents:
import '@babel/polyfill';
# How to dynamically modify the title?
The title can be dynamically modified via react-helmet.
Note: In a hybrid application, if you use react-helmet in the ios web container, you can try react-document-title.
# Reporting Error
# Object.values
is not a function
E.g.
Upgrade the node version and make sure the version is 8.10 or greater.
# exports is not defined
E.g.
Check the babel configuration to remove unnecessary presets and plugins.
# Plugin umi-plugin-react:pwa initialize failed
E.g.
Make sure you have package.json and have configured the name
attribute.
# Conflicting order between [mini-css-extract-plugin]
E.g.
This is a problem with the webpack plugin, which does not affect the normal production of CSS files and can be ignored for now.
# umi
is not an internal or external command
E.g.
You need to configure the NODE_PATH environment variable. If you use yarn, you can get the bin path by executing yarn global bin
.
# webpack
# How to configure additional loader?
For example, I hope .svg not to produce base64, but to generate svg files, which can be configured like this:
export default {
// Add exclude for url-loader
urlLoaderExcludes: [/.svg$/],
// Add loader
chainWebpack(config) {
config.module
.rule('svg-with-file')
.test(/.svg$/)
.use('svg-with-file-loader')
.loader('file-loader');
},
};
# CSS
# Why don't my imported CSS files take effect?
umi use css modules by default, please write your css as css modules.
Ref:
# How to disable CSS modules?
Modify .umirc.js
:
{
"disableCSSModules": true
}
However, it is not recommended to turn off css modules for no particular reason.
# How to use sass?
Install additional dependencies first,
$ npm i node-sass sass-loader --save
Then modify .umirc.js
:
{
"sass": {}
}
# Test
# How to do breakpoint debugging?
Make sure node version is above 8.10 and then execute:
$ node --inspect-brk ./node_modules/.bin/umi test
Then open chrome://inspect/#devices in the browser for inspect and breakpoints.
# Deployment
# After the build access route is refreshed 404?
Several options are available:
- Use
hashHistory
instead ofhistory: 'hash' in
.umirc.js` - Static, with
exportStatic: true
in.umirc.js
- The server configures the route fallback to index.html
# After the build, the picture is lost?
It may be that the picture is not correctly quoted. You can refer to the code and import the picture correctly.
import React from 'react';
import logo from './logo.png'; // Tell Webpack this JS file to use this image
console.log(logo); // logo.84287d09.png
function header() {
// import image
return <img src={logo} alt="Logo" />;
}
export default Header;
Use in css, be careful not to use absolute paths
.Logo {
background-image: url(./logo.png);
}
Note: base64 will be taken when the image size is less than 10 k. That is, it will not be copied to the public folder, but will be stored as a base64 resource.
# SSR
# document is not defined, navigator is not defined, * is not not defined
Why: Umi SSR executes code first server-side, then client-side. The document
, navigator
object is only present client-side. Solution:
- you absolutely need to have access to it in some React component, you should put that code in
componentDidMount
oruseEffect
. This lifecycle method will only be executed on the client. - add the judgment with something like
typeof navigator !== 'undefined'
ortypeof document !== 'undefined'
# SSR has no style, style loading is wrong
Why: The publicPath of the Umijs configuration does not match the route of the server. When the resource path such as /umi.js
is accessed, it is not mapped correctly to the specified file. solution:
- Try to access the link
http://yourHost/umi.js
orhttp://yourHost/dist/umi.js
to see which link returns the correct js/css file contents. - Correspond to modify the
publicPath
path.
# styled-components build error
Add babel-plugin-styled-components babel pluign. #3508
// .umirc.js
extraBabelPlugins: [
"babel-plugin-styled-components"
],
# UMI UI
# Umi version is too low, please upgrade to umi@2.9 or above
Umi UI requires umi@2.9 or above, and this error will be reported if the version of the local project does not match.
The solution is to upgrade to the latest version.
- If the umi dependency in package.json is automatically matched to the latest version, such as
^ 2.9
or2.x
, delete thenode_modules
reload dependency. - If the umi dependency in package.json does not match the latest version, such as
~2.8
or2.8.0-beta.1
, then it needs to be changed to^ 2.9
or other matching to the latest version, then Removenode_modules
and reload dependencies
# EACCES: permission denied create-umi
Umi UI needs to have permission to create projects.
The solution is to raise the prompted path permissions and give execute permissions.ã