We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
首先克隆仓库后,运行了 build
$ npm run build
这时会卡在 91%,然后我把 这一行 改成了:
"build": "TS_CONFIG_PATHS_PLUGIN=none cross-env BABELRC=1 umi build
这时 build 成功了。
这里想问下,上次 sorrycc 说 TS_CONFIG_PATHS_PLUGIN 在 umijs 后面的版本会自动忽略,现在是否是忽略了 umi dev 相关的,但umi dev 相关的并没有忽略?另外 TS_CONFIG_PATHS_PLUGIN 写在 cross-env 前面会影响后面的 BABELRC=1 么?
umi dev
TS_CONFIG_PATHS_PLUGIN
cross-env
BABELRC=1
然后参考了以下 issues:
以及其他的 serve 相关的 issues,在 dist 目录下运行:
serve
$ serve -s -p 8000
然后网页打开 localhost:8000 后,logo 显示不出来,输入 admin 的账号密码后,点击登录后控制台报错:
SyntaxError: expected expression, got '<'
The text was updated successfully, but these errors were encountered:
提示不影响使用。 另外接口使用,参考#832
Sorry, something went wrong.
No branches or pull requests
部署过程:
首先克隆仓库后,运行了 build
这时会卡在 91%,然后我把 这一行 改成了:
这时 build 成功了。
这里想问下,上次 sorrycc 说 TS_CONFIG_PATHS_PLUGIN 在 umijs 后面的版本会自动忽略,现在是否是忽略了
umi dev
相关的,但umi dev
相关的并没有忽略?另外TS_CONFIG_PATHS_PLUGIN
写在cross-env
前面会影响后面的BABELRC=1
么?然后参考了以下 issues:
以及其他的
serve
相关的 issues,在 dist 目录下运行:具体问题
然后网页打开 localhost:8000 后,logo 显示不出来,输入 admin 的账号密码后,点击登录后控制台报错:
The text was updated successfully, but these errors were encountered: