[NervJS/taro] beta5升级到v3.0.0正式版后,在development下vendor.js体积多了400k (#6853)

From: notifications@github.com
Domain: IP info github.com
MX-server: IP info out-24.smtp.github.com
Size: 5897 Bytes
Create: 2020-07-01
Update: 2020-07-01
Score: 1
Safe: Yes

Outbound domains: github.com |

问题描述
beta5升级到v3.0.0正式版后,在development下vendor.js体积多了400k

复现步骤

  1. yarn add @taro/cli & taro update project v3.0.0
  2. 相比v3.0.0-beta5的development下主包体积大了400多k,导致无法预览
  3. 比较两个版本后的vendor.js会发现多了以下诸多模块(可能列的不完全)
var COMMENT_KEYS = exports.COMMENT_KEYS = ["leadingComments", "trailingComments", "innerComments"];
  1. 本地package.json
"dependencies": {
		"@babel/runtime": "^7.7.7",
		"@tarojs/components": "3.0.0",
		"@tarojs/react": "3.0.0",
		"@tarojs/runtime": "3.0.0",
		"@tarojs/taro": "3.0.0",
		"mobx": "^5.15.4",
		"mobx-react": "^6.2.2",
		"react": "^16.10.0",
		"react-dom": "^16.10.0",
		"taro-ui": "3.0.0-alpha.2"
	},
	"devDependencies": {
		"@babel/core": "^7.8.0",
		"@tarojs/cli": "3.0.0",
		"@tarojs/mini-runner": "3.0.0",
		"@tarojs/webpack-runner": "3.0.0",
		"@types/react": "^16.0.0",
		"@types/webpack-env": "^1.13.6",
		"babel-preset-taro": "3.0.0",
		"eslint": "^6.8.0",
		"eslint-config-taro": "3.0.0",
		"eslint-plugin-import": "^2.12.0",
		"eslint-plugin-react": "^7.8.2",
		"eslint-plugin-react-hooks": "^1.6.1",
		"stylelint": "9.3.0"
	}

期望行为
正式版和beta5版本相当的打包体积

报错信息

正式版比beta5同等条件下多了四百多k的大小

系统信息
Taro CLI 3.0.0 environment info:
System:
OS: macOS 10.14.6
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.8.1 - /usr/local/bin/node
Yarn: 1.22.4 - ~/.yarn/bin/yarn
npm: 6.10.2 - /usr/local/bin/npm
npmPackages:
@tarojs/cli: 3.0.0 => 3.0.0
@tarojs/components: 3.0.0 => 3.0.0
@tarojs/mini-runner: 3.0.0 => 3.0.0
@tarojs/react: 3.0.0 => 3.0.0
@tarojs/runtime: 3.0.0 => 3.0.0
@tarojs/taro: 3.0.0 => 3.0.0
@tarojs/webpack-runner: 3.0.0 => 3.0.0
babel-preset-taro: 3.0.0 => 3.0.0
eslint-config-taro: 3.0.0 => 3.0.0
react: ^16.10.0 => 16.13.1
taro-ui: 3.0.0-alpha.2 => 3.0.0-alpha.2
npmGlobalPackages:
typescript: 3.2.2

补充信息
[可选]


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Want to protect your real email from messages like this? Use TempM email and be more secure on the internet.