.babelrc

@@ -1,16 +0,0 @@
-{
-  "env": {
-    "test": {
-      "presets": [
-        [
-          "@babel/preset-env",
-          {
-            "targets": {
-              "node": "current"
-            }
-          }
-        ]
-      ]
-    }
-  }
-}

.editorconfig

@@ -1,13 +0,0 @@
-# editorconfig.org
-root = true
-
-[*]
-indent_style = space
-indent_size = 2
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false

.gitignore

@@ -1,94 +0,0 @@
-# Created by .ignore support plugin (hsz.mobi)
-### Node template
-# Logs
-/logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-.history/
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-
-# nyc test coverage
-.nyc_output
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# Bower dependency directory (https://bower.io/)
-bower_components
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (https://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directories
-node_modules/
-jspm_packages/
-
-# TypeScript v1 declaration files
-typings/
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# dotenv environment variables file
-.env
-
-# parcel-bundler cache (https://parceljs.org/)
-.cache
-
-# next.js build output
-.next
-
-# nuxt.js build output
-.nuxt
-
-# Nuxt generate
-dist
-
-# vuepress build output
-.vuepress/dist
-
-# Serverless directories
-.serverless
-
-# IDE / Editor
-.idea
-
-# Service worker
-sw.*
-
-# macOS
-.DS_Store
-
-# Vim swap files
-*.swp
-
-env.js

.npmrc

@@ -1,2 +0,0 @@
-registry=https://registry.npm.taobao.org/
-sass_binary_site="https://npm.taobao.org/mirrors/node-sass"

Dockerfile

@@ -1,13 +0,0 @@
-FROM node:14.17.0
-WORKDIR /workload
-
-COPY nuxt.config.js /workload/nuxt.config.js
-COPY package.json /workload/package.json
-COPY .nuxt /workload/.nuxt
-COPY static /workload/static
-
-RUN npm config set registry https://registry.npm.taobao.org \
-    && npm install
-
-EXPOSE 3000
-CMD npm run start

README.md

@@ -1,161 +1,92 @@
-<!--
- * @Author: ch
- * @Date: 2022-05-05 15:39:29
- * @LastEditors: ch
- * @LastEditTime: 2022-05-07 11:39:38
- * @Description: file content
--->
-
 # shop-pc
 
-## 前置环境
+马士兵严选pc 
 
-由于项目依赖问题，开发 `node` 版本必须是 `14`。
+## Getting started
 
-如果电脑安装 `Node 18`，那么怎么添多个 `node` 版本，可以使用 `nvm` 版本管理工具。具体安装可以参考下面教程
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
 
-[window install nvm](https://juejin.cn/post/7074108351524634655)
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-[mac install nvm](https://juejin.cn/post/7206882855200047161)
 
-## 修改前端接口请求地址
+## Add your files
 
-进入到 ` plugins/config/env.js` 中：
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
 
-```js
+```
-// 修改对应值即可
+cd existing_repo
-const ENV = {
+git remote add origin http://internel-git.mashibing.cn/yanxuan-frontend/shop-pc.git
-  base_url: "https://k8s-horse-gateway.mashibing.cn",
+git branch -M main
-  imUrl: "wss://k8s-horse-gateway.mashibing.cn",
+git push -uf origin main
-};
-export default ENV;
 ```
 
-> `注意 ⚠️`：通常本地开发访问线上接口地址时会出现跨越(协议、域名、端口不一样时就会出现跨越问题)，此时后端服务需要配置跨域相关的内容。
+## Integrate with your tools
 
-## 运行&打包
+- [ ] [Set up project integrations](http://internel-git.mashibing.cn/yanxuan-frontend/shop-pc/-/settings/integrations)
 
-- 运行直接执行 npm run dev 打包执行 npm run build 即可，会根据分支读取不同环境变量配置；
+## Collaborate with your team
 
-## 环境变量配置
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
 
-- 环境变量配置文件 env.config;
+## Test and Deploy
-- 配置与分支对应关系：msb_prod -> prod msb_beta -> beta msb_test -> test msb-其他 -> dev
-- 输出的环境变量文件：plugins/config/env.js
-- 修改环境变量配置后需要执行 “ node env.config " 输出的环境变量才会更新
 
-```js
+Use the built-in continuous integration in GitLab.
-// 直接引入输出的配置文件即可
-import ENV from "@/plugins/config/env.js";
-// 直接访问你在配置文件中定义的属性
-console.log(ENV.baseUrl);
-```
 
-## 公共方法 utils
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- 公共方法统一放置 utils 文件夹内，可以按分类建方法文件 如：验证类 verify.js 请求类 request.js；
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- 所有公共方法采用大驼峰命名法
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- 所有的方法都从 index.js 输出，引入时统一引入 index，不允许直接引入方法文件
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-- 所有方法文件如果导出的是多个方法，不允许在定义方法时导出，必须在文件底部一一导出，并附上方法简单的注释
-
-```js
-// 正确
-import {Req, IsPhone} from '@/common/utils';
-
-// 错误
-import {Req} from '@/common/utils/request';
-import {IsPhone} from '@/common/utils/utils';
-
-// 正确
-const IsPhone = (str) => {....}
-const IsEmail = (str) => {....}
-export {
-	// 判断手机号
-	IsPhone,
-	// 判断邮箱
-	IsEmail
-}
-```
 
-## 组件
+***
 
-- 根目录的 components 只放置真正的组件，某个页面的业务模块应该在 pages 的相应目录下新建 module 目录放置
+# Editing this README
-- 所有的自定义组件文件名以大驼峰命名，且在 templet 中使用也用大驼峰形式使用(包括页面内的模块组件)
 
-## storage 的使用
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!).  Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
 
-- 不要在页面内直接使用 loaclStorage，全都放置到 vuex 中做一次管理
+## Suggestions for a good README
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
 
-## 请求
+## Name
+Choose a self-explaining name for your project.
 
-- 项目中有两个 axios 请求实例，一个事 nuxt 自带的（不需要 Token 请使用这个），一个是额外封装的（需要 Token 请使用这个）；
+## Description
-- 需要 Token 的请求，不要写在 asyncData 中；
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-- 所有请求方法命名以（Api+请求类型+具体方） 法命名
-- 所有请求使用 ToAsyncAwait 包裹
-- 不允许使用 try catch 和 then 处理返回结果
 
-```js
+## Badges
-// 使用示例
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-	// xxapi.js
-	import {ToAsyncAwait, ReqestTk} from '@/common/utils'
-	const ApiGetUserInfo = (parapms) => ToAsyncAwait(ReqestTk.get('xxxxUrl',{params}));
-	exprot {
-		// 获取用户信息
-		ApiGetUserInfo
-	}
-	// user.vue
-	improt {ApiGetUserInfo} from '@/common/api/xxapi.js';
 
-	const getUserInfo = async () =>{
+## Visuals
-		const {error, result} = await ApiGetUserInfo();
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-		if(error){
-			alert(error);
-			return false;
-		}
-		app.userInfo = result;
-	}
 
-```
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
 
-## css
+## Usage
-
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-- 采用 BEM 命名法
-
-### 兼容 CSS
-
-```css
-/* 以下兼容方式的样式请使用util.css中的adj方法 */
-.my-class {
-  transform: translate3d(-50%, 0, 0);
-  -webkit-transform: translate3d(-50%, 0, 0);
-  -moz-transform: translate3d(-50%, 0, 0);
-  -o-transform: translate3d(-50%, 0, 0);
-  -ms-transform: translate3d(-50%, 0, 0);
-}
-/* 使用以下方法 */
-@import "~/assets/scss/util.scss";
-.my-class {
-  @include adj(transform, translate3d(-50%, 0, 0));
-}
-```
 
-## 登录相关
+## Support
-
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-```javascript
+
-// 访问token
+## Roadmap
-this.$store.state.token;
+If you have ideas for releases in the future, it is a good idea to list them in the README.
-// 设置token
+
-this.$store.commit("setToken");
+## Contributing
-// 退出登录
+State if you are open to contributions and what your requirements are for accepting them.
-this.$store.commit("setLoginOut");
+
-// 获取登录的用户信息
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-this.$store.state.userInfo;
+
-
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-// 登录拦截
+
-// 示例：点击购买课程前需要判断当前用户是否登录，未登录则弹出登录弹窗
+## Authors and acknowledgment
-function onPurchaseCourse() {
+Show your appreciation to those who have contributed to the project.
-  if (!this.$isLoginValidate()) {
+
-    return;
+## License
-  }
+For open source projects, say how it is licensed.
-  // 此处省略其他业务代码...
+
-}
+## Project status
-```
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.