如今做vue的相关开发，基本都离不开vue-cli，有时候，我们也会将自己工作中抽象出来的优秀方法或者组件发布给外网进行使用，本文基于自身写的seed组件系统整理一下如何自动化发布到npm的一个流程
一些前期准备
github账号和仓库地址npmjs的账号
整体构建流程
既然要做，就考虑一下完全自动化构建发布吧，基于github actions来完成整个CI/CD工作，主要包含，代码的自动构建，自动发布文档到github.io以及自动发布到npm上
所以我们需要
vue-cli创建项目github code用于在github action的时候访问授权npmjs code发布的时候用的codevuepress可以在md中使用vue组件的文档构建工具一些合理的命名，在组件发布到
npm后，调用者也能正确的使用
开始安装vue-cli
请老手直接跳过
npm install -g @vue/cli
# OR
yarn global add @vue/cli
vue create 你的项目名称
更改你的目录结构
初始化的vue项目目录基本是为了开发一个网页app使用的，然而我们的目标是构建一个lib所以需要将目录结构进行一定的更改
原本的src文件夹存放的是页面的源代码，在组件库构建中，相当于是一个演示目录，所以我们将其更名为examples, 同时在根目录下新建一个packages存放我们开发的lib需要的代码，当然，如果有一些通用的lib文件的话，也新建一个lib文件夹好了
既然目录结构改了，一些默认的入口地址也进行更换
增加jsconfig.json
这个主要为了方便vscode提示，大概例子为
{
"compilerOptions": {
"target": "esnext",
"experimentalDecorators": true,
"baseUrl": ".",
"checkJs": false,
"paths": {
"@/*": [
"./examples/*"
],
"{你的项目名称}/packages/*": [
"./packages/*"
],
"{你的项目名称}/lib/*": [
"./lib/*"
],
"types/*": [
"types/*"
]
}
},
"exclude": [
"node_modules",
"lib",
"docs",
".github",
"public"
]
}
增加vue.config.js
这里为了做别名引用，以及修改开发时的页面的入口文件地址为新的目标文件夹
同时解决打包组件库会多css文件的问题，当然，如果需要单独打包css可以不配置css相关
const path = require("path");
function resolve(dir) {
return path.join(__dirname, dir);
}
module.exports = {
chainWebpack: config => {
config.resolve.alias
.set("@", resolve("examples"))
.set("{项目名称}/packages", resolve("packages"))
.set("{项目名称}/lib", resolve("lib"));
},
pages: {
index: {
entry: "examples/main.js",
template: "public/index.html",
filename: "index.html"
}
},
css: { extract: false }
};
package.json
主要修改scripts下的build为"build": "vue-cli-service build --target lib --dest dist --name 项目名 packages/库的入口文件或者库的vue文件"
同时增加
"files": [
"packages/",
"dist",
"lib/",
"README.md",
"types/",
"LICENSE"
],
"main": "dist/{打包的文件名}.umd.min.js",
编写代码
之后你可以尽情编写代码了，examples下文件的别名还是@/*，自身开发的库的文件以及库的调用通过你的项目名/具体路径来进行调用即可，之后就愉快的开发吧
文档
文档我们选用vuepress方便将例子渲染在docs的页面内，当然，本教程也只会提供一些基础的配置
安装
npm i --save-dev vuepress
在package.json的scripts中增加
"docs:dev": "npx vuepress dev docs",
"docs:build": "npx vuepress build docs",
创建文件夹和配置文件
在根目录创建docs以后文档都会在这个目录底下，同时我们在docs下创建.vuepress文件夹
vuepress的具体配置请查看官网，这里列出一些需要增加的配置
在.vuepress文件夹下增加config.js 同时增加内容
const path = require("path");
function resolve(dir) {
return path.resolve(__dirname, '..', '..', dir);
}
module.exports = {
chainWebpack: (config) => {
config.resolve.alias
.set("@", resolve("examples"))
.set("{项目名称}/packages", resolve("packages"))
.set("{项目名称}/lib", resolve('lib'))
}
};
在.vuepress文件夹下增加components文件夹，并新建Example.vue
输入内容
<template>
<ClientOnly>
<App />
</ClientOnly>
</template>
<script>
import App from "@/App";
export default {
components: {
App
},
};
</script>
这样就能将examples下的例子在文档内直接引用了
<Example />
当然，多个例子可以通过prop或者新建多个vue文件等不同办法实现
顺带一提，如果想要实现预览源码，可以使用prism.js配合jsdelivr来实现，我这里直接放出具体demo
<template>
<div v-if="sourceCode" class="source-code">
<div class="language-vue extra-class">
<pre
class="language-vue"
><code ref="code" v-html="sourceCode" /></pre>
</div>
</div>
</template>
<script>
import prism from 'prism'
export default {
data() {
return {
sourceCode: ''
}
},
methods: {
handleShowSourceCode() {
fetch(
`https://cdn.jsdelivr.net/gh/{github用户名}/{项目名}@master/examples/{App}.vue`
)
.then(function(response) {
return response.text();
})
.then(function(raw) {
vm.sourceCode = prism.highlight(raw, prism.languages.markup, "vue");
})
}
}
}
</script>
自动化
接下来就是github actions的时间了，这里我们将设置如果master分支有变化，则构建docs同时如果tag有增加，则构建对应的tag版本的release和推送到npmjs
主要靠三个action配置文件 以及 先把你的
构建文档
这里我们需要配置一个DEPLOY_KEY到github.secreat里 其实就是公钥和私钥啦，本地ssh-keygen之后，将私钥贴在github.setting的deploy_key中，将公钥放在github.setting.secreat中，并命名为DEPLOY_KEY
.github/workflows/doc.yml
name: Publish docs to github actions
on:
push:
branches:
- master
jobs:
build-and-deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2 # If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
with:
persist-credentials: false
- name: Install
run: npm ci && npm run-script docs:build
- name: Install SSH Client
uses: webfactory/ssh-agent@v0.2.0 # This step installs the ssh client into the workflow run. There's many options available for this on the action marketplace.
with:
ssh-private-key: ${{ secrets.DEPLOY_KEY }}
- name: Build and Deploy Repo
uses: JamesIves/github-pages-deploy-action@releases/v3
with:
BASE_BRANCH: master
BRANCH: gh-pages
FOLDER: docs/.vuepress/dist
SSH: true # SSH must be set to true so the deploy action knows which protocol to deploy with.
发布release
需要申请当前仓库的release权限，并配置为GH_TOKEN,请参考github的官方配置
增加一个changelog命令到package.json的scripts中"changelog": "npx conventional-changelog -p angular -i ./dist/CHANGELOG.md -s -r 0"
.github/workflows/release.yml
name: upload release asset
on:
push:
# Sequence of patterns matched against refs/tags
tags:
- "v*" # Push events to matching v*, i.e. v1.0, v20.15.10
jobs:
build:
name: Upload Release Asset
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2 # If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
with:
persist-credentials: false
- name: Install
run: npm ci && npm run build && npm run changelog
- name: Read Changelog
id: read_changelog
uses: GenesisSam/get-simple-file-action@v1.0.4
with:
file-name: ${{ './dist/CHANGELOG.md' }}
- name: Build project # This would actually build your project, using zip for an example artifact
run: zip -r lib.zip dist
- name: Create Release
id: create_release
uses: actions/create-release@v1.0.0
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
with:
tag_name: ${{ github.ref }}
release_name: Release ${{ github.ref }}
body: ${{ steps.read_changelog.outputs.data }}
draft: false
prerelease: false
- name: Upload Release Asset
uses: actions/upload-release-asset@v1.0.1
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
with:
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
asset_path: ./lib.zip
asset_name: lib.zip
asset_content_type: application/zip
发布到npm
需要事先在npm申请auth token，并在github的仓库配置中，配到NPM_TOKEN上
点击头像在auth tokens上申请即可
.github/workflows/npm.yml
name: publish to npm
on:
push:
tags:
- "v*" # Push events to matching v*, i.e. v1.0, v20.15.10
pull_request:
tags:
- "v*" # Push events to matching v*, i.e. v1.0, v20.15.10
jobs:
publish:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2 # If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
with:
persist-credentials: false
- name: Install
run: npm ci && npm run build
- name: publish
uses: JS-DevTools/npm-publish@v1
with:
token: ${{ secrets.NPM_TOKEN }}
这样，一个自动工作的vue库文件开发工作流就完成啦，愉快的开发吧
还有一件事
如何快速打tag?利用npm version {版本类型}即可
如果在package.json的scripts中增加"postversion": "git push --follow-tags"甚至连发布工作都会自动帮你做掉，还等什么呢！