CLI tool for Arco Design

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. MacOS]
• node version [e.g. v16.13.1]

Additional context Add any other context about the problem here.

• [ ] I'm sure this does not appear in the issue list of the repository

基本信息

• 依赖包名 及 版本: new
• 浏览器版本: chrome99.0.4844.74
• 复现地址: http://baidu.com

预期结果

正常创建

看图

• [x] I'm sure this does not appear in the issue list of the repository

Basic Info

• 依赖包名 及 版本: @arco-design/arco-cli 1.21.1
• 系统版本: mac os big sur 11.5.2
• 浏览器版本: No
• 复现地址: https://github.com

额外补充

$ tsc && cp -rf src/scripts/changelog/template/ lib/scripts/changelog/template
Done in 14.02s.
lerna info run Ran npm script 'build' in '@arco-design/arco-cli-block' in 8.8s:
yarn run v1.22.10
$ tsc
Done in 8.33s.
lerna ERR! yarn run build exited 127 in '@arco-design/arco-components'
lerna ERR! yarn run build stdout:
yarn run v1.22.10
$ arco-scripts build:component:es && arco-scripts build:component:css
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

lerna ERR! yarn run build stderr:
/bin/sh: arco-scripts: command not found
error Command failed with exit code 127.

lerna ERR! yarn run build exited 127 in '@arco-design/arco-components'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @arco-design/[email protected] preRelease: `lerna run clean && lerna run build`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the @arco-design/[email protected] preRelease script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/lambert/.npm/_logs/2021-10-28T14_13_21_057Z-debug.log

预期结果

能够本地构建成功，并在本地debug

复现步骤

node -v: v12.22.1 yarn -v: 1.22.10

git clone npm run init npm run preRelease

Is your feature request related to a problem? Please describe. No.

Describe the solution you'd like To support an existed storybook site quick convert to standard arco-material-doc-site as a team site.

Describe alternatives you've considered No.

Additional context No.

• [ ] I'm sure this does not appear in the issue list of the repository

Basic Info

• Package Name And Version: [email protected]
• Browser: chrome98.0.4758.109
• Reproduction Link: https://codesandbox.io/s/fervent-bush-i68nts

Extra info

这个不需要提供 Reproduction Link 我就瞎写了一个。

What is expected?

.gitignore 中有dist，package.json中有build脚本

Steps to reproduce

1. 安装acro-cli最新版
2. acro init test 选择 react -> vite -> acroDesignPro -> 简单模版 生成项目文件

Types of changes

• [ ] New feature
• [x] Bug fix
• [ ] Documentation change
• [ ] Coding style change
• [ ] Refactoring
• [ ] Performance improvement
• [ ] Test cases
• [ ] Continuous integration
• [ ] Typescript definition change
• [ ] Breaking change

Background and context

Solution

How is the change tested?

Changelog

| Changelog(CN) | Changelog(EN) | Related issues | | ------------- | ------------- | -------------- |

Checklist:

• [ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
• [ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to master branch)

Other information

Describe the bug 新建vue 组件库物料项目安装后报如下错误 DeprecationWarning: Default PostCSS plugins are deprecated. When switching to '@storybook/addon-postcss', you will need to add your own plugins, such as 'postcss-flexbugs-fixes' and 'autoprefixer'.

See https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated-default-postcss-plugins for details. (Use node --trace-deprecation ... to show where the warning was created) 0% compilingERR! TypeError: Cannot read properties of undefined (reading 'get')

To Reproduce Steps to reproduce the behavior:

1. arco init demo
2. 选择vue
3. 选择组件库, 输入npm包名，输入物料标题，输入描述，输入npm版本号0.1.0，选择关键词
4. 等待下载依赖
5. yarn install 后yarn dev报错

Expected behavior

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS10.15.7
• node version [e.g. v16.15.0]
• arco-cli [v1.27.1] Additional context Add any other context about the problem here.

Describe the bug PS C:\Users***\Desktop\study_vue\hello-arco-pro> arco init hello-arco-pro

    ___                    ____            _
   /   |  ______________  / __ \___  _____(_)___ _____
  / /| | / ___/ ___/ __ \/ / / / _ \/ ___/ / __ `/ __ \
 / ___ |/ /  / /__/ /_/ / /_/ /  __(__  ) / /_/ / / / /
/_/  |_/_/   \___/\____/_____/\___/____/_/\__, /_/ /_/
                                         /____/

                                            v1.26.1

? 请选择你希望使用的技术栈 Vue ? 请选择所要创建项目的类型 Arco Pro 项目 ? 请选择 Arco Pro 模板 完整版（包含所有页面）

正在初始化项目于 C:\Users***\Desktop\study_vue\hello-arco-pro\hello-arco-pro √ 获取项目模板成功 × 模板内容拷贝失败 Error: Failed to copy project content. npm WARN config global --global, --local are deprecated. Use --location=global instead.

at module.exports (C:\Users\***\.arco_template_cache\1655866434222\node_modules\arco-design-pro-vue\.arco-cli\init.js:25:13)
at C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\arco-cli-create-project\lib\index.js:129:23
at Generator.next (<anonymous>)
at fulfilled (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\arco-cli-create-project\lib\index.js:5:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5)

Error: EBUSY: resource busy or locked, rmdir 'C:\Users***.arco_template_cache\1655866434222\node_modules\arco-design-pro-vue' node:fs:1180 return handleErrorFromBinding(ctx); ^

Error: EBUSY: resource busy or locked, rmdir 'C:\Users*.arco_template_cache\1655866434222\node_modules\arco-design-pro-vue' at Object.rmdirSync (node:fs:1180:10) at rmdirSync (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:264:13) at rimrafSync (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:243:7) at C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:279:39 at Array.forEach () at rmkidsSync (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:279:26) at rmdirSync (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:269:7) at rimrafSync (C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:243:7) at C:\Program Files\node-v16.15.1-win-x64\node_modules\node_global\node_modules\arco-cli\node_modules\fs-extra\lib\remove\rimraf.js:279:39 at Array.forEach () { errno: -4082, syscall: 'rmdir', code: 'EBUSY', path: 'C:\Users\*\.arco_template_cache\1655866434222\node_modules\arco-design-pro-vue' }

To Reproduce Steps to reproduce the behavior:

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: win10
• node version v16.15.1

Additional context Add any other context about the problem here.

Describe the bug 如标题

To Reproduce Steps to reproduce the behavior: 安装npm i arco-cli -g 初始化arco init yourProjectName

Expected behavior 能成功执行

Screenshots

Desktop (please complete the following information):

• OS: Windows10
• node version v16.13.1

Other Content 虽然提示初始化完成，可以启动，但是执行npm run dev也是报错

升级 arco-scripts 依赖

• [email protected] 已经和 [email protected]~8 存在不兼容的情况，只能将两者的版本写死；
• less 版本无法平稳升级到 ~4；
• 升级依赖可能需要发布 arco-scripts 的大版本。

• [ ] I'm sure this does not appear in the issue list of the repository

Basic Info

What are the similar cases of this feature

--

What problem does this feature solve?

这样就不用有个临时目录了，看着难受

Extra info

see https://github.com/webpack/webpack/issues/6437#issuecomment-874358637

• [x] I'm sure this does not appear in the issue list of the repository

Basic Info

https://github.com/arco-design/arco-cli/blob/main/packages/arco-cli-auth/src/login.ts#L66

现有案例

N/A

预期解决问题

When arco login or arco env --switch on a remote machine, the post-login redirection to http://localhost:3333/login_result is impossible to succeed since arco login is listening on a remote devbox instead of localhost.

额外补充

Suggested solution: Grab all IP addresses of the os and prompt user with selection or manual input

🐛 Bug Fix

• Fix the bug that build failed caused by ts-loader.

🐛 Bug Fix

• Fix the bug that arco publish fails to execute due to the failure to fetch the Git remote repository.

🚀 Feature

• Added arco group --link command to link accounts to a specified group.
• Allow group users to use custom category alternatives when initing project, and allow custom inputs.

🐛 Bug Fix

• When run arco generate, if arco Meta.json exists, the check of arcoMeta field in package.json should be skipped.

🐛 Bug Fix

• Fix the bug that style compilation fail due to styleConfig.hook.beforeCompile/afterCompile not specify.

🚀 Feature

• Add config.hook.beforeCompile/afterCompile configuration for style build to customize the behavior before/after style files compilation.

🐛 Bug Fix

• Fix the bug that TS compilation may fail due to specifying Babel to compile ESM/CJS products and extending the include field through tsconfig.json.

🐛 Bug Fix

• Fix the problem that command executed failed caused by child_process.spawnSync on Windows platform.

💎 Enhancement

• Use child_process.spawn to replace spawnSync/execSync methods to avoid UI blocking caused by sync methods.