tencent / feflow

🚀 A command line tool aims to improve front-end engineer workflow and standard, powered by TypeScript.

English | 简体中文

Feflow

🚀 A tool aims to improve front-end engineer workflow and standard, powered by TypeScript.

Introduction

Feflow is an engineering solution of Tencent's open source front-end field, which is committed to improving development efficiency and specification.

Getting Started

Let's start by installing Feflow with npm.

npm install @feflow/cli -g

There are three kinds of commands in Feflow

• Native Commands
  • fef config
  • fef help
  • fef info
  • fef install
  • fef uninstall
  • fef list

You can write a Feflow devkit or plugin to extends commands.

More detail document can be found:

• Github Wiki
• Website

Change Log

This project adheres to Semantic Versioning. Every release, along with the migration instructions, is documented on the GitHub Releases page.

License

MIT

feflow's Issues

feflow init 本地代理存在问题时，提示信息需要优化

For BUG

本地代理存在问题时，运行feflow init，会经过两个步骤，两个步骤之间间隔时间较长

1. 界面没有任何提示，30s+
   

2. 提示更新，最后失败
   

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined

For BUG

执行feflow build时，报错，如下图：

构建器：
builderType: builder-webpack3

Feflow 会覆盖插件的参数

例如，运行 feflow deploy -h 的时候，显示的其实是 feflow -h 的结果，应该是 feflow 率先获取到 -h 参数，就打印帮助信息了，这里不合理，应该先调用插件，把参数传给插件，而不是覆盖

支持脚本创建新项目

For Feature

希望能支持：

1. 通过脚本创建项目
2. 支持配置的方式传入所需参数
3. 配置支持配置多个页面，通过脚手架生成的项目包含多个页面

初始化时输入registry和proxy时如果多了空格会报错

For BUG

1. BUG description
   初始化时输入registry和proxy时如果多了空格会报错

2. The way to reproduce
   node: v6.11.3
   npm: 3.10.10
   feflow: v0.11.2

3. Log with feflow --debug
   

Feflow 插件参数不支持大写吗

如图所示，无论是 -m 还是 -M ，都被解析成 m

提供清除 .feflow 下面的内容的命令

feflowjs.org 官网支持 https 访问

For feature request

首次使用feflow提示Fatter error.

For BUG

1. 安装 feflow 之后首次使用初始化时运行 $ feflow init 时报错

3. felow v0.13.1
node v6.9.5

文档修改建议：脚手架不存在

For BUG

在文档 脚手架开发 中，提及 generator-now-activity、generator-now-business 两个脚手架。

安装的时候提示404。

npm install -g generator-now-activity

希望 feflow.json 写的 webpack 跨域的配置能在构建器里面生效

主要是团队的构建器需要支持 feflow.json 的跨域配置

支持命令行直接完成feflow初始化

第一次使用feflow的时候，需要交互式输入npm的registry和npm的proxy完成初始化。
但在build docker镜像的时候，不能交互式输入，所以没办法完成Feflow的初始化步骤
希望可以支持命令行直接完成初始化的功能

feflow 所有命令报错问题

For BUG

当第一次使用 feflow 的时候
出现输入 register，但是这个 register 可能有用户输入出错，比如

现在使用feflow -h，出现

这个时候，想要使用 feflow config 重新设置正确的 register，但是还是出现如下（设置register失效）：

使用其他命令

也就是说第一次用户如果输入 register 错误的话，将会导致一切命令都失效，重新设置都无效，必须将~/.feflow目录删除，才能重新输入正确的 register。建议添加一些容错处理。

For question

For feature request

运行到init之后链路就断了

feflow init
? 请输入npm的registry: http://registry.npmjs.org
? 请输入npm的proxy(默认为空): 
Feflow INFO  初始化完成，请输入命令开启feflow的使用之旅。(帮助：feflow -h)

运行完init，什么也没生成，也没有变化，不知道要干什么？文档指引不够清晰

feflow init 提示没有模版

For question

两个内置脚手架是下了吗？feflow install 提示 not found ，还是需要自定义脚手架?

支持通过js模块配置项目元数据

目前通过feflow.json配置构建数据，json文件无法编程，存在很多限制

支持js模块配置构建数据

运行feflow dev或者feflow build 需要进行增量更新检测和升级

For feature request

运行feflow dev或者feflow build 需要进行增量更新检测和升级。否则，构建器发布了新版本，没办法自动让用户进行更新。

更新的版本还是根据某个包的package.json里面的campatibleVersion字段进行判断

  "configs": {
    "compatibleVersion": ">=0.1.3"
  }

希望 feflow 支持 react native

主机名与RTX名不同导致feflow init失败

For BUG

问题描述

主机名、RTX名不同，导致feflow init过程失败。

环境描述：

• osx：10.13.6 (17G65)
• feflow：v0.14.1
• nodejs：v6.14.4

重现步骤

1. feflow init 之后，选择模板基于 React + Redux + Webpack 的 web 业务开发解决方案。
2. 初始化过程的应答：自动申请monitor id、badjs id、离线包、创建 git 项目

Site link is broken

For BUG

using chrome go to page: https://www.feflowjs.org
ERR_CONNECTION_RESET

For question

For feature request

feflow install 提示有误

For BUG

1. BUG description
   • feflow install 时如果某个插件存在，并且没有安装，初始版本为undefined，应该为null.
   • feflow install时如果插件不存在，提示都是 检测到您本地安装的已经是最新的插件，无需重复安装
2. feflow版本是v0.10.0

清风团队接入后，脚手架运行完后报 undefined 错误

未安装脚手架，初次运行feflow init，给出的提示信息不够明确

For feature request

初次安装feflow-cli，运行feflow init，控制台提示如下

Feflow WARN  检测到你还未安装任何模板，请先安装后再进行项目初始化，参考文档：https://github.com/iv-web/feflow-cli/blob/master/README.md

根据提示信息，跳转到 https://github.com/iv-web/feflow-cli/blob/master/README.md，并没有任何有用信息

建议：

1. 给出具体的操作指引
2. 提示信息给到的链接，能跳到该指引

初始化npm 仓库写错了，proxy也写错了导致出错

For question

错误代码：
Feflow ERROR cli core全量更新失败，失败码为1，

问题 | 进展 | 完成时间

问题	进展	完成时间
插件/套件中未注入feflow实例	进行中
插件/套件初始化失败	进行中
help命令未注册倒是运行报错	进行中
bin命令设置有问题，未指向index.js	进行中
feflow实例的args为空	进行中

feflow 支持本地构建器

能否在feflow.json中定义

builderType: false

的时候无需全局安装构建器，而是交给模板里的webpack配置处理。
feflow dev运行时可以自动改为运行npm start

希望报错能够有友好地提示或处理

这个可能需要梳理一下目前可能遇到的错误，以及处理方案

windows10项目下运行feflow -v时会报错

For BUG

林江反馈：应该是操作系统的原因，在windows10 上项目的根目录执行 feflow -v 时，会弹出如下错误，我怀疑是什么机制导致你的 feflow 命令 和这个 feflow.js 建立了某些关系；因为当我cd src 里面再执行 feflow -v 时，就是正常的

服务器部署需要手动指定 package manager

For BUG

然后就部署失败了。。。

For question

For feature request

官网打不开

网站暂时无法访问
该网站未根据工信部相关法律规则进行备案
可能因为以下原因:
原因一: 该网站未根据工信部要求完成备案

如何进行网站备案?

原因二: 该网站可能存在不适宜传播的内容

更多备案帮助，可咨询客服

建议安装脚手架和构建器时增加参数--global-style

npm将node_modules扁平化安装，导致构建器或者脚手架的依赖互相影响，比如安装builder-webpack3时会在.feflow下安装webpack3，而使用builder-webpack4时会寻找到webpack3，导致构建报错。

npm install --global-style能避免此问题

相关issue #feflow/builder-webpack4#12

上报功能在 IDC 机器上网络不通

For BUG

希望可以支持不开启cdn的模式

For feature request

希望可以支持不开启cdn的模式
比如在 builderOptions 中传 cdn: '' 就可以默认不使用cdn

bug: missing dependencies

1. bug description: feflow init 后, tnpm start时提示缺少依赖（已执行$ feflow install feflow-plugin-deps $ feflow deps --global）

2. dev environment:

   • node v9.1.0
   • npm v5.5.1
   • tnpm v5.0.11
   • macOS 10.13.1

3. bug log:

    [WARNI] Can't resolve `@tencent/util` in file [/actions/appStatus.js], did you miss `npm install @tencent/util`?
   ..
    [WARNI] Can't resolve `@tencent/util` in file [/assets/business/downloader.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `@tencent/now-jsbridge` in file [/assets/business/ui.js], did you miss `npm install @tencent/now-jsbridge`?
   
    [WARNI] Can't resolve `@tencent/util` in file [/assets/business/ui.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/assets/business/ui.js], did you miss `npm install @tencent/device`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/config/config.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/assets/config/config.js], did you miss `npm install @tencent/device`?
   .
    [WARNI] Can't resolve `react-fastclick` in file [/assets/global/global.js], did you miss `npm install react-fastclick`?
   
    [WARNI] Can't resolve `@tencent/imweb-react-mixin` in file [/assets/global/global.js], did you miss `npm install @tencent/imweb-react-mixin`?
   .
    [WARNI] Can't resolve `@tencent/modjs` in file [/assets/global/lib.js], did you miss `npm install @tencent/modjs`?
   
    [WARNI] Can't resolve `@tencent/promise` in file [/assets/global/lib.js], did you miss `npm install @tencent/promise`?
   
    [WARNI] Can't resolve `redux` in file [/assets/global/lib.js], did you miss `npm install redux`?
   
    [WARNI] Can't resolve `redux-thunk` in file [/assets/global/lib.js], did you miss `npm install redux-thunk`?
   
    [WARNI] Can't resolve `react-dom` in file [/assets/global/lib.js], did you miss `npm install react-dom`?
   
    [WARNI] Can't resolve `react-redux` in file [/assets/global/lib.js], did you miss `npm install react-redux`?
   
    [WARNI] Can't resolve `react-fastclick` in file [/assets/global/lib.js], did you miss `npm install react-fastclick`?
   
    [WARNI] Can't resolve `humps` in file [/assets/global/lib.js], did you miss `npm install humps`?
   ...
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/base64.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/dom.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/index.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/mqq.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/now-util-mqq` in file [/assets/utils/mqq.js], did you miss `npm install @tencent/now-util-mqq`?
   
    [WARNI] Can't resolve `@tencent/now-util-device` in file [/assets/utils/mqq.js], did you miss `npm install @tencent/now-util-device`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/open.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/assets/utils/open.js], did you miss `npm install @tencent/device`?
   
    [WARNI] Can't resolve `@tencent/fake-protocol` in file [/assets/utils/open.js], did you miss `npm install @tencent/fake-protocol`?
   
    [WARNI] Can't resolve `@tencent/visibility-state` in file [/assets/utils/open.js], did you miss `npm install @tencent/visibility-state`?
   
    [WARNI] Can't resolve `@tencent/tx-send` in file [/assets/utils/open.js], did you miss `npm install @tencent/tx-send`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/proj.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/assets/utils/proj.js], did you miss `npm install @tencent/device`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/qqapi.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/assets/utils/time.js], did you miss `npm install @tencent/util`?
   ...
    [WARNI] Can't resolve `@tencent/db` in file [/middleware/api.js], did you miss `npm install @tencent/db`?
   
    [WARNI] Can't resolve `humps` in file [/middleware/api.js], did you miss `npm install humps`?
   ...
    [WARNI] Can't resolve `@tencent/tx-monitor` in file [/middleware/report.js], did you miss `npm install @tencent/tx-monitor`?
   ..
    [WARNI] Can't resolve `@tencent/fake-protocol` in file [/modules/common/framework-util.js], did you miss `npm install @tencent/fake-protocol`?
   
    [WARNI] Can't resolve `@tencent/huatuo` in file [/modules/common/framework-util.js], did you miss `npm install @tencent/huatuo`?
   .
    [WARNI] Can't resolve `@tencent/fake-protocol` in file [/modules/common/frameworkUtil.js], did you miss `npm install @tencent/fake-protocol`?
   
    [WARNI] Can't resolve `@tencent/huatuo` in file [/modules/common/frameworkUtil.js], did you miss `npm install @tencent/huatuo`?
   .
    [WARNI] Can't resolve `@tencent/util` in file [/modules/common/wordingRandom.js], did you miss `npm install @tencent/util`?
   .
    [WARNI] Can't resolve `react` in file [/modules/components/dialog/index.js], did you miss `npm install react`?
   ..
    [WARNI] Can't resolve `react` in file [/modules/components/download-bar/index.js], did you miss `npm install react`?
   
    [WARNI] Can't resolve `react-redux` in file [/modules/components/download-bar/index.js], did you miss `npm install react-redux`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/modules/components/download-bar/index.js], did you miss `npm install @tencent/device`?
   
    [WARNI] Can't resolve `@tencent/util` in file [/modules/components/download-bar/index.js], did you miss `npm install @tencent/util`?
   ..
    [WARNI] Can't resolve `@tencent/util` in file [/modules/components/download-bar/report.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/aop` in file [/modules/components/download-bar/report.js], did you miss `npm install @tencent/aop`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/modules/components/download-bar/report.js], did you miss `npm install @tencent/device`?
   .
    [WARNI] Can't resolve `react` in file [/modules/components/progress_loading/index.js], did you miss `npm install react`?
   
    [WARNI] Can't resolve `react-redux` in file [/modules/components/progress_loading/index.js], did you miss `npm install react-redux`?
   ..
    [WARNI] Can't resolve `react` in file [/modules/components/titlebar/index.js], did you miss `npm install react`?
   
    [WARNI] Can't resolve `classnames` in file [/modules/components/titlebar/index.js], did you miss `npm install classnames`?
   
    [WARNI] Can't resolve `@tencent/now-jsbridge` in file [/modules/components/titlebar/index.js], did you miss `npm install @tencent/now-jsbridge`?
   ....
    [WARNI] Can't resolve `redux` in file [/modules/globalStore/Store.js], did you miss `npm install redux`?
   
    [WARNI] Can't resolve `redux-thunk` in file [/modules/globalStore/Store.js], did you miss `npm install redux-thunk`?
   .
    [WARNI] Can't resolve `react` in file [/modules/page/BasePage.js], did you miss `npm install react`?
   
    [WARNI] Can't resolve `react-dom` in file [/modules/page/BasePage.js], did you miss `npm install react-dom`?
   
    [WARNI] Can't resolve `react-redux` in file [/modules/page/BasePage.js], did you miss `npm install react-redux`?
   
    [WARNI] Can't resolve `@tencent/tx-monitor` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/tx-monitor`?
   
    [WARNI] Can't resolve `@tencent/imweb-report` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/imweb-report`?
   
    [WARNI] Can't resolve `@tencent/huatuo` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/huatuo`?
   
    [WARNI] Can't resolve `@tencent/badjs-report` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/badjs-report`?
   
    [WARNI] Can't resolve `@tencent/util` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/util`?
   
    [WARNI] Can't resolve `@tencent/now-jsbridge` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/now-jsbridge`?
   
    [WARNI] Can't resolve `@tencent/fake-protocol` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/fake-protocol`?
   
    [WARNI] Can't resolve `@tencent/device` in file [/modules/page/BasePage.js], did you miss `npm install @tencent/device`?
   ....
    [WARNI] Can't resolve `@tencent/report-whitelist` in file [/pages/activity/index.html], did you miss `npm install @tencent/report-whitelist`?

附近的项目需要接入到 generator-now-webpack

For BUG

For question

For feature request

fef init 的时候需要注意当前仓库下有无重名文件夹

建议读取一下当前目录下的文件列表，如和用户新建的项目名称重复，警告用户是删除重建还是重新命名。

For BUG

For question

For feature request

node-sass 的问题？

希望 feflow init 命令支持传递自定义的配置文件

在写脚手架时，需要能够传递一个本地的配置文件，例如 webpack 就支持这种命令 webpack --config webpack.config.js。

希望能够支持 feflow init --config ./a/b/c.js 这种，然后将 ./a/b/c.js 转换成绝对路径 /user/a/b/c.js 传递到 generator 脚手架中，由脚手架获得这个文件之后，自行进行处理

feflow package.json main指向文件有问题

For BUG

in package.json main 指向./lib/index.js，但是应该指向./lib/feflow.js

update 错误

For BUG

pkgJson方法获取最新版本时返回404 error

期望新版feflow可以支持js后缀配置文件

#108 For feature request
期望新版feflow可以支持js后缀配置文件

关于插件安装问题

For bug

在开发插件时，把插件安装到devDependencies中无法运行，发现源码中优先获取dependencies依赖，如果有，就不再获取devDependencies中的依赖，导致命令注册失败

我自己弄了个脚手架， 自己电脑可以用fe init看到模板；怎么让团队里面的其他人fe init也能看到呢？

For BUG

For question

For feature request

fef dev、build命令只能在项目根目录运行是吗？

这个issue来源企鹅电竞接入方反馈

希望插件的使用可以更加灵活（pipeline化）

通过这个项目的接入体验之后，个人感觉最大的痛点是目前一个插件一个命令，导致操作分散，缺乏 pipeline 的概念。

在目前的版本看来，现在一个插件对应为一个命令，这就导致了如果我引入多个插件时需要运行多个插件命令才能完成固化的某个阶段性任务。例如，在发布阶段，自动化部署 => 接口文档更新（插件） => 发布 changelog （插件），需要手工对应地运行多个插件命令，而不是直接通过拓展 npm run build 命令来自动化串联任务。

所以，基于以上，对此的诉求是：希望插件的引入可以 pipeline 化，通过指定某个命令执行就可以完成多个插件命令的串联执行。

建议如果feflow init后脚手架未创建成功加个报错信息提示

For BUG

For question

For feature request

v0.16.0 alpha灰度版本问题反馈

windows 下偶发创建项目卡住

For BUG

system: windows10
node: v10.13.0

使用命令feflow init 命令行卡住

建议构建器支持生产环境开启sourcemap生成

监控上报系统如badjs、sentry可以支持sourcemap还原报错代码位置，但需要将编译生成的sourcemap文件上传至监控系统服务器。
所以希望feflow增加一个配置项允许开启生产环境生成sourcemap，满足上述需求。

无法正常clone代码

For question

当我clone代码时显示：

git clone https://github.com/feflow/feflow.git
Cloning into 'feflow'...
remote: Counting objects: 1248, done.
remote: Compressing objects: 100% (154/154), done.
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed