https://github.com/mritd/tpclash

使用起来也非常简单。

1. 首先先把它下载下来，重命名为 /usr/local/bin/clash

2. 创建 clash 的工作目录，可以是任何目录，我放在了 /etc/clash

3. 增加配置文件 config.yaml

    interface-name: ens18 # 请指定自己实际的接口名称(ip a 获取)
   
    port: 7890
    socks-port: 7891
    redir-port: 7892
    tproxy-port: 7893
    allow-lan: true
    bind-address: "*"
    mode: Rule
    log-level: info
    external-controller: 0.0.0.0:9090
    secret: ""
    external-ui: /opt/clash-dashboard
   
    dns:
      enable: true
      ipv6: false
      listen: 0.0.0.0:1053
      enhanced-mode: fake-ip
      fake-ip-range: 198.18.0.1/16
      default-nameserver:
        - 114.114.114.114
        - 1.1.1.1
      nameserver:
        - 114.114.114.114
        - 223.6.6.6
   
    tun:
      enable: true
      stack: system
      auto-route: true
      auto-detect-interface: true
      dns-hijack:
        - any:53
   
    proxies:
      - {
          name: hk,
          udp: true,
        }
   
    rule-providers:
      reject:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/reject.txt"
        path: ./ruleset/reject.yaml
        interval: 86400
   
      icloud:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/icloud.txt"
        path: ./ruleset/icloud.yaml
        interval: 86400
   
      apple:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/apple.txt"
        path: ./ruleset/apple.yaml
        interval: 86400
   
      google:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/google.txt"
        path: ./ruleset/google.yaml
        interval: 86400
   
      proxy:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/proxy.txt"
        path: ./ruleset/proxy.yaml
        interval: 86400
   
      direct:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/direct.txt"
        path: ./ruleset/direct.yaml
        interval: 86400
   
      private:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/private.txt"
        path: ./ruleset/private.yaml
        interval: 86400
   
      gfw:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/gfw.txt"
        path: ./ruleset/gfw.yaml
        interval: 86400
   
      greatfire:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/greatfire.txt"
        path: ./ruleset/greatfire.yaml
        interval: 86400
   
      tld-not-cn:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/tld-not-cn.txt"
        path: ./ruleset/tld-not-cn.yaml
        interval: 86400
   
      telegramcidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/telegramcidr.txt"
        path: ./ruleset/telegramcidr.yaml
        interval: 86400
   
      cncidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/cncidr.txt"
        path: ./ruleset/cncidr.yaml
        interval: 86400
   
      lancidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/lancidr.txt"
        path: ./ruleset/lancidr.yaml
        interval: 86400
   
      applications:
        type: http
        behavior: classical
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/applications.txt"
        path: ./ruleset/applications.yaml
        interval: 86400
   
    rules:
      - RULE-SET,applications,DIRECT
      - DOMAIN-SUFFIX,hashnode.com,hk
      - DOMAIN-KEYWORD,taobao,DIRECT
      - DOMAIN-KEYWORD,github,hk
      - DOMAIN,clash.razord.top,DIRECT
      - DOMAIN,yacd.haishan.me,DIRECT
      - RULE-SET,private,DIRECT
      - RULE-SET,reject,REJECT
      - RULE-SET,icloud,DIRECT
      - RULE-SET,apple,DIRECT
      - RULE-SET,google,DIRECT
      - RULE-SET,proxy,hk
      - RULE-SET,direct,DIRECT
      - RULE-SET,lancidr,DIRECT
      - RULE-SET,cncidr,DIRECT
      - RULE-SET,telegramcidr,hk
      - GEOIP,LAN,DIRECT
      - GEOIP,CN,DIRECT
      - MATCH,DIRECT # 处理漏网之鱼，可按需调整为默认走 proxy 或像我一样默认 direct
   

4. 启动测试，看下配置是否有误

    clash --test
   

5. 注册为服务，方便使用 systemctl 控制

    # /etc/systemd/system/clash.service
    [Unit]
    Description=Clash TProxy
    After=network.target
   
    [Service]
    User=root
    Group=clash
    Restart=on-failure
    ExecStart=/usr/local/bin/clash -d /etc/clash
   
    [Install]
    WantedBy=multi-user.target
   

6. 启动服务，并配置开机自启

    systemctl start clash
    systemctl enable clash
   

7. 将自己的设备网关设置为运行服务的机器 ip, Over

PS. tpclash 作者同样提供了 docker 配置方案

先给出(从同事那借来的)配置：

version: "3"

services:
  # Enable ip_forward - https://askubuntu.com/a/311054
  # For Ubuntu Server, you also need to disable systemd-resolved
  # 1. sudo systemctl stop systemd-resolved
  # 2. sudo systemctl disable systemd-resolved
  clash:
    image: dreamacro/clash-premium
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    network_mode: "host"
    volumes:
      - ./clash:/root/.config/clash
    restart: "always"
    logging:
      driver: "json-file"
      options:
        max-size: "5m"

port: 7890
socks-port: 7891
redir-port: 7892
allow-lan: true
bind-address: "*"
mode: Rule
log-level: info
external-controller: 0.0.0.0:9090
secret: "secret"
dns:
  enable: true
  listen: 0.0.0.0:1053
  ipv6: true
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  nameserver:
    - 223.5.5.5
    - 223.6.6.6

tun:
  enable: true
  stack: system
  auto-route: true
  auto-detect-interface: true

proxies:
  - name: "hk"
    type: trojan
    server: server
    port: 443
    password: password


proxy-groups:
  - name: Proxy-Fallback
    type: fallback
    proxies:
      - hk
      - DIRECT
    url: 'http://www.gstatic.com/generate_204'
    interval: 3

  - name: Proxy
    type: select
    proxies:
      - Proxy-Fallback

rule-providers:
  apple-proxy:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/Hackl0us/SS-Rule-Snippet@master/Rulesets/Clash/Basic/Apple-proxy.yaml"
    path: ./ruleset/Apple-proxy.yaml
    interval: 86400
  apple-direct:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/Hackl0us/SS-Rule-Snippet@master/Rulesets/Clash/Basic/Apple-direct.yaml"
    path: ./ruleset/Apple-direct.yaml
    interval: 86400
  china:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/China.yaml"
    path: ./ruleset/China.yaml
    interval: 86400
  global:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Global.yaml"
    path: ./ruleset/Global.yaml
    interval: 86400
  netflix:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/Hackl0us/SS-Rule-Snippet@main/Rulesets/Clash/App/stream/Netflix.yaml"
    path: ./ruleset/Netflix.yaml
    interval: 86400
  disney:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/Hackl0us/SS-Rule-Snippet@main/Rulesets/Clash/App/stream/DisneyPlus.yaml"
    path: ./ruleset/Disney.yaml
    interval: 86400
  lan:
    type: http
    behavior: classical
    url: "https://cdn.jsdelivr.net/gh/Hackl0us/SS-Rule-Snippet@master/Rulesets/Clash/Basic/LAN.yaml"
    path: ./ruleset/LAN.yaml
    interval: 86400

rules:
  # Rule sets
  - RULE-SET,apple-proxy,Proxy
  - RULE-SET,apple-direct,Proxy
  - RULE-SET,china,DIRECT
  - RULE-SET,global,Proxy
  - RULE-SET,lan,DIRECT
  # Final rules
  - GEOIP,CN,DIRECT
  - MATCH,Proxy

然后 docker compose up -d

当然以上只是把 Clash 跑起来，宿主机仍然需要设置转发规则来转发流量到 clash dns：

# https://zhuanlan.zhihu.com/p/423684520
REDIR_PORT="7892"
CLASH_DNS_PORT="1053"

#在nat表中新建一个clash规则链
iptables -t nat -N CLASH
#排除环形地址与保留地址，匹配之后直接RETURN
iptables -t nat -A CLASH -d 0.0.0.0/8 -j RETURN
iptables -t nat -A CLASH -d 10.0.0.0/8 -j RETURN
iptables -t nat -A CLASH -d 127.0.0.0/8 -j RETURN
iptables -t nat -A CLASH -d 169.254.0.0/16 -j RETURN
iptables -t nat -A CLASH -d 172.16.0.0/12 -j RETURN
iptables -t nat -A CLASH -d 192.168.0.0/16 -j RETURN
iptables -t nat -A CLASH -d 224.0.0.0/4 -j RETURN
iptables -t nat -A CLASH -d 240.0.0.0/4 -j RETURN
#重定向tcp流量到本机 redir_host
iptables -t nat -A CLASH -p tcp -j REDIRECT --to-port "$REDIR_PORT"
#拦截外部tcp数据并交给clash规则链处理
iptables -t nat -A PREROUTING -p tcp -j CLASH

#在nat表中新建一个clash_dns规则链
iptables -t nat -N CLASH_DNS
#清空clash_dns规则链
iptables -t nat -F CLASH_DNS
#重定向udp流量到本机 clash dns
iptables -t nat -A CLASH_DNS -p udp -j REDIRECT --to-port "$CLASH_DNS_PORT"
#抓取本机产生的53端口流量交给clash_dns规则链处理
iptables -t nat -I OUTPUT -p udp --dport 53 -j CLASH_DNS
#拦截外部upd的53端口流量交给clash_dns规则链处理
iptables -t nat -I PREROUTING -p udp --dport 53 -j CLASH_DNS

之后把各种设置或主路由的 dns 网关设置为宿主机 ip 就可以翻墙了。

但是仍然有一个问题，clash 在跑的情况下宿主机不能联网了，应该是以上路由规则存在问题，正在与 ChatGPT 激情讨论中

references:

• https://github.com/Lienol/openwrt
• https://mianao.info/2020/05/05/%E7%BC%96%E8%AF%91%E6%9B%B4%E6%96%B0OpenWrt-PassWall%E5%92%8CSSR-plus%E6%8F%92%E4%BB%B6

uh-oh

更奇怪的一点是，普通的 http 请求是可以访问到的:

猜测和 npm 仓库的相应策略有关系，但是等对应部门给出解决方案不太现实，所以只好自己试试把 .npmrc 替换为 .yarnrc

好吧，没想到问题就这么解决了，所以在这里只能给大家提供一个建议：

⚠️ yarn 尽量使用 .yarnrc 来指定项目 config

毫无疑问，配置大部分是针对 rules的。

以下给出的配置都假设你的 webpack.config.js位于项目根目录下。

## optimization 部分

// 使用 terser 代替 uglify-js
const TerserPlugin = require('terser-webpack-plugin');
const isWsl = require('is-wsl');

// optimization
{
  // Keep the runtime chunk separated to enable long term caching
    // https://webpack.js.org/configuration/optimization/#optimizationruntimechunk
    runtimeChunk: true,

minimizer: [
    new TerserPlugin({
           terserOptions: {
               parse: {
                   // we want uglify-js to parse ecma 8 code. However, we don't want it
                   // to apply any minfication steps that turns valid ecma 5 code
                   // into invalid ecma 5 code. This is why the 'compress' and 'output'
                   // sections only apply transformations that are ecma 5 safe
                   // https://github.com/facebook/create-react-app/pull/4234
                   ecma: 8,
               },
               compress: {
                   ecma: 5,
                   warnings: false,
                   // Disabled because of an issue with Uglify breaking seemingly valid code:
                   // https://github.com/facebook/create-react-app/issues/2376
                   // Pending further investigation:
                   // https://github.com/mishoo/UglifyJS2/issues/2011
                   comparisons: false,
                   // Pending futher investigation:
                   // https://github.com/terser-js/terser/issues/120
                   inline: 2,
               },
               mangle: {
                   safari10: true,
               },
               output: {
                   ecma: 5,
                   comments: false,
                   // Turned on because emoji and regex is not minified properly using default
                   // https://github.com/facebook/create-react-app/issues/2488
                   ascii_only: true,
               },
           },

// Use multi-process parallel running to improve the build speed
           // Default number of concurrent runs: os.cpus().length - 1
           // https://github.com/webpack-contrib/terser-webpack-plugin/issues/21
           parallel: !isWsl,
           // Enable file caching
           cache: true,
           sourceMap: false,
           exclude: /\.min\.js$/,
       }),
  ]
}

## 针对 js(x) 文件的配置

rules

{
    test: /\.(js|jsx|mjs)$/,
    exclude: [/[/\\\\]node_modules[/\\\\]/],
    use: [
        'thread-loader',
        {
            loader: require.resolve('babel-loader'),
            options: {
                compact: true,
                configFile: './.babelrc',
                // 对项目 js 代码 transpile 的结果进行持久化缓存
                cacheDirectory: '.cache/babel',
                // 缓存文件不做 gzip 压缩，
                //当你的代码文件数量比较多时建议配置此项为 false
                cacheCompression: false,
            },
        },
        {
            loader: require.resolve('eslint-loader')，
            options: {
        // 对 lint 的结果进行缓存
                cache: '.cache/eslint',
            },
        },
    ],
},

plugins

// 再另一个进程里进行对 ts 的类型检查
new ForkTsCheckerWebpackPlugin({
    tsconfig: './tsconfig.json',
    // block webpack's emit to wait for type checker/linter and to add errors to the webpack's compilation
    // also required for the the overlay functionality of webpack-dev-server
    async: false,
    // checkSyntacticErrors is required as we use happyPackMode and the thread-loader to parallelise the builds
    checkSyntacticErrors: true,
}),

## 针对 ts(x) 文件的配置

const ForkTsCheckerWebpackPlugin = require(‘fork-ts-checker-webpack-plugin’);

const os = require(‘os’)
const cpus = os.cpus().length
// 需要给 fork-ts-checker-webpack-plugin 分配 1 个
const tsLoaderWorkers = cpus > 2 ? cpus — 1 : 1

rules

{
    test: /\.(tsx?|d.ts)$/,
    include: 'src',
    use: [
        {
            // 启用基于文件的缓存
            loader: require.resolve('cache-loader'),
            options: {
                cacheDirectory: '.cache/cache-loader',
            },
        },
        {
            loader: require.resolve('thread-loader'),
            options: {
                workers: tsLoaderWorkers,
            },
        },
        {
            loader: require.resolve('ts-loader'),
            options: {
       /**
        * Increase build speed by disabling typechecking for the
        * main process and is required to be used with thread-loader
        * [@see](http://twitter.com/see) [https://github.com/TypeStrong/ts-loader/blob/master/examples/thread-loader/webpack.config.js](https://github.com/TypeStrong/ts-loader/blob/master/examples/thread-loader/webpack.config.js)
        * Requires to use the ForkTsCheckerWebpack Plugin
        */
                happyPackMode: true,
                configFile: `./tsconfig.json`,
            },
        },
    ],
},

plugins

// 在另一个进程里进行对 ts 的类型检查
new ForkTsCheckerWebpackPlugin({
    tsconfig: './tsconfig.json',
    // block webpack's emit to wait for type checker/linter and to add errors to the webpack's compilation
    // also required for the the overlay functionality of webpack-dev-server
    async: false,
    // checkSyntacticErrors is required as we use happyPackMode and the thread-loader to parallelise the builds
    checkSyntacticErrors: true,
}),

## 效果

当前项目代码量

https://yarnpkg.com

在项目中，我们的项目结构很有可能是下面的情况：

.

├── packages

│   ├── module-a

│   │      └── package.json

│   ├── module-b

│   │      └── package.json

│   └── share

│   │      └── package.json (react-dnd@3.0.0)

└── package.json (react-dnd@9.3.0)

我们有三个 worksapce，分别是 module-a module-b share，module-a/module-b 都依赖了根目录下的 react-dnd@9，而 share 则依赖了 react-dnd@3.

在 build 时，share 下的代码如果出现了 import { DndProvider } from ‘react-dnd’ 类似内容的话，被打包的会是根目录下的 node_modules/react-dnd@9，而不是 share/node_modules/react-dnd@3.

根据我的个人理解，因为 workspace 是把所有的依赖都放到了项目根目录下，即使你在 share 下的 package.json 声明了你需要的 react-dnd@3，在打包时得到的依然会是根目录下的 react-dnd@9

如何处理这种情况呢？聪明的同学可能已经想到了，我们使用 yarn 的特性同时安装两个版本的 react-dnd 就好了。

yarn add react-dnd-v3@npm:react-dnd@3.0.0

然后把引用旧版本的 react-dnd 都修改为 react-dnd-v3

一般情况下到这里，上面的问题就应该解决了，可是我们还有问题。

react-dnd@3 和 react-dnd@9 都依赖了 hoist-non-react-statics，而前者需要的是 2.x，后者需要的是 3.x!

这种情况下我们就需要把 share/node_modules 与根目录下的 node_modules 隔离开了，让 share 下保留 react-dnd@3，根目录下保留 react-dnd@9，同时将它们各自的依赖安装在自己的 node_module 下

再查了一下文档，发现了 [nohoist](https://yarnpkg.com/blog/2018/02/15/nohoist/)

...
  "name": "app",
  "private": true,
  "workspaces": {
    "packages": [
                  "packages/share", 
                  "packages/module-a", 
                  "packages/module-b"
    ],
    "nohoist": ["share/react-dnd", "share/react-dnd/**"]
  }
  ...

完成上述步骤就 ok 啦

针对 CapsLock 键:

• 单击* 切换输入法(本质是调用 win + sapce*)

• 双击/长按 切换 CapsLock 状态

preview

以下是脚本内容:

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
;#Persistent
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.

hideTrayTip() {
    TrayTip  ; Attempt to hide it the normal way.
    if SubStr(A_OSVersion,1,3) = "10." {
        Menu Tray, NoIcon
        Sleep 200  ; It may be necessary to adjust this sleep.
        Menu Tray, Icon
    }
}


switchCapsLockState() {
    state := GetKeyState("CapsLock", "T")
    nextState := !state
    SetCapsLockState % nextState

    return nextState
}

showTip(isOn) {
    title := isOn ? "CapsLock: ON" : "CapsLock: OFF"
    text := isOn ? "已打开" : "已关闭"

    TrayTip, %title%, %text%, 0, 16
    Sleep 1000
    hideTrayTip()

    return 
}

toggleAndShowTip() {
    nextState :=switchCapsLockState()
    showTip(nextState)

    return
}

CapsLock::
    KeyWait, CapsLock, T0.2

    if (ErrorLevel) {
        ; long click
        toggleAndShowTip()
    } else {
        KeyWait, CapsLock, D T0.1

        if (ErrorLevel) {
            ; single click
            Send #{Space}
        } else {
            ; double click
            toggleAndShowTip()
        }
    }

    KeyWait, CapsLock

return

Webpack-dev-server is sweet, but when you have some routes in your back end and have to handle them with other logic instead just redirect them to your spa, webpack-dev-middleware may be one of your options.

We can use webpack-dev-middleware along with express, but here is one problem. Except routes mentioned above, you still need to respond remaining requests with your index page, especially when html-webpack-plugin is involved, because when we enabled HMR, the compiled index page only exists in memory, we don’t know it’s precise location.

So here is the solution: HtmlWebpackPlugin + webpack-dev-middleware other pathname than / · Issue #145 ·… Hello, First, thank you for your wonderful work! Second ,) My issue, I tried to use HtmlWebpackPlugin with dev server…github.com

var express = require('express');
var app = express();
var webpack = require('webpack');
var path = require('path');

var compiler = webpack(require('./webpack.config.js'));

var devMiddleware = require('webpack-dev-middleware');

app.use(devMiddleware(compiler, {
  noInfo: true,
  publicPath: '/'
}));

app.use('*', function (req, res, next) {
  var filename = path.join(compiler.outputPath,'index.html');
  devMiddleware.waitUntilValid(() => {
    compiler.outputFileSystem.readFile(filename, function(err, result){
      if (err) {
        return next(err);
      }
      res.set('content-type','text/html');
      res.send(result);
      res.end();
    });
  });
});

app.listen(3000);

准备

> 树莓派 x1

> 公网 ip x1（打客服电话问运营商）

初始化

在拿到树莓派以后先安装系统（废话），找 SD卡槽找了半天，后来在发现原来在背面 😶

安装系统的时候还有一个大坑，按照官方说的使用 Etcher 写入 SD 卡根本进入不了系统…后面搜索了一番用 Win32 Disk Imager 才搞定。

进入系统之后首先打开树莓派的设置界面，启用 SSH、关闭图形界面（节省资源，毕竟是要长期跑着+没有一个多余的显示器给它插）。

Shadowsocks 配置

安装 Shadowsocks 的部分倒是没有太多好说的，执行 apt install 就可以了，配置可以参考下面：

{

“server”:”0.0.0.0",

“server_port”:8388,

“local_port”:1080,

“password”:”pwd”,

“timeout”:300,

“method”:”rc4-md5",

“fast_open”: false,

“workers”: 1

}

由于我们要在路由器里给它分配 ip，所以这里的 server 部分就填 0.0.0.0 就可以了。

路由器配置

这里我的路由器使用的是 Padavan，别的系统的设置请自行查找。

首先我们要先给树莓派一个固定 ip，然后设置端口转发(高级设置 → 外部网络 (WAN) → 端口转发 (UPnP) )。设置内容如下图所示：

端口转发设置

下面就可以配置 DDNS 了。

配置 DDNS

这里我们使用的是 ddclient + namecheap 的域名。

ddclient 配置文件默认在 /etc/ddclient.conf ，内容如下：

use=web, web=dynamicdns.park-your-domain.com/getip

protocol=namecheap

server=dynamicdns.park-your-domain.com

# 以下内容需要修改

login=example.com #你的域名

password=xxxpasswordxxx #你的密码

subdomain #你的二级域名

设置完成以后，执行 ping 测试一下吧，如果返回结果就是你的公网 ip 就大工搞成了！

因此，我们需要给 Upload 这个组件传入 额外的 token、key. 根据官方文档，传入额外的参数只需要给它加上 data 这个属性就可以了，对应的值是一个 Object.

<Upload {…otherProps} data={{ token: ‘xxxx:token’, key: ‘xxx:key’ }} />

具体的代码如下:

import { Upload } from 'antd'

const uploadProps = {
  action: `https://up-z2.qiniu.com`,
  name: 'file',
  listType: 'picture-card',
  className: 'avatar-uploader'
}

class UploadImg extends Component {
  state = {
    token: null,
    key: null,
    domain: null,
    loading: false,
  }

  componentDidMount() {
    getImgUploadToken()
      .then(({ token, key, domain }) => {
        this.setState({
          token,
          key,
          domain
        })
      })
  }

  handleAvatarChange = ({ file }) => {
    if (file.status === 'uploading') {
      this.setState({ loading: true })
      return
    }
    if (file.status === 'done') {
      const { response: { hash } } = file
      const imageSrc = `${this.state.domain}${hash}`

      updateProfilePic(imageSrc)
        .then(() => {
          console.log('上传成功')
        })
    }
  }

  render() {
    const { token, key } = this.state
    const {
      user,
      imageUrl,
      form: { getFieldDecorator }
    } = this.props

    return (
      <Upload {...uploadProps}
        className={'profile-uploader'}
        accept="image/*"
        showUploadList={false}
        data={{ token, key }}
        beforeUpload={beforeUpload}
        onChange={this.handleAvatarChange}>
        <img src={imageUrl}
          style={{
            width: '102px',
            height: '102px'
          }}
          alt="" />
      </Upload>
    )
  }
}

export default UploadImg

npm install — save jquery

然后在 webpack.dev.config.js 文件中，添加

// plugins 区块内
 new webpack.ProvidePlugin({
   $ : “jquery”,
   jQuery : “jquery”,
   “window.jQuery”: “jquery”,
   “root.jQuery” : “jquery”
 })

随后安装 semantic-ui-css

npm install semantic-ui-css — save

之后在 webpack.base.config.js 文件中添加，

// resolve 区块
 resolve : {
 extensions: [‘’, ‘.js’, ‘.vue’],
 fallback : [path.join(__dirname, ‘../node_modules’)],
 alias : {
   ‘vue’ : ‘vue/dist/vue.common.js’,
   ‘src’ : path.resolve(__dirname, ‘../src’),
   ‘assets’ : path.resolve(__dirname, ‘../src/assets’),
   ‘components’: path.resolve(__dirname, ‘../src/components’),
   // Semantic-UI
   ‘semantic’ : path.resolve(__dirname, ‘../node_modules/semantic-ui-css/semantic.min.js’)
 }
 }

随后在 webpack.dev.config.js 文件中，添加

plugins: [
   new webpack.ProvidePlugin({
     $ : “jquery”,
     jQuery : “jquery”,
     “window.jQuery”: “jquery”,
     “root.jQuery” : “jquery”,
     // Semantic-UI
     semantic : ‘semantic-ui-css’,
     Semantic : ‘semantic-ui-css’,
     ‘semantic-ui’: ‘semantic-ui-css’
 }),

接下来，引入 css 和 js 文件:

import semantic from ‘semantic’
import ‘../node_modules/semantic-ui-css/semantic.min.css’

接下来，我们要测试一下，添加一个 vue 文件：

<template>
  <div class="semantic-component">
    <div class="ui selection dropdown semanticDropDown">
      <input type="hidden" name="gender" v-model="selected">
      <i class="dropdown icon"></i>
      <div class="default text">Gender</div>
      <div class="menu">
        <div class="item" :data-value="item.Value"
             v-for="item in items"
             [@click](http://twitter.com/click)="changeSelection(item)">
          {{ item.Gender }}
        </div>
      </div>
    </div>
    <pre>{{ JSON.stringify(selectedItem) }}</pre>
  </div>
</template>

<script>
  export default {
    data() {
      return {
        items       : [
          {Gender: 'Male', Value: 1},
          {Gender: 'Female', Value: 0}
        ],
        selected    : '',
        selecteditem: {}
      }
    },
    methods: {
      changeSelection(item) {
        this.selectedItem = item
        this.selected = item.Value
      }
    },
    mounted() {
      this.selecteditem = {}
      $(this.$el).find('.semanticDropDown').dropdown()
    }
  }
</script>

<style></style>

参考链接：Using vue.js with semantic UI