云手机相关H5前端,小程序,云手机,云游戏等

曾志翔 e9716b3d25 feat(活动邀请用户赚星币): 唤起app 2 lat temu
api eb7583af69 feat(api): 修改api模块加载模式 3 lat temu
assets 1c6f79f9e1 feat(邀请用户活动): 按钮 2 lat temu
layouts 899ca5d5df feat(nuxt): vant有个bug更换为vuetify 3 lat temu
modules a856b2c1b0 fix(活动邀请好友赚星币): 修复取值错误 2 lat temu
pages e9716b3d25 feat(活动邀请用户赚星币): 唤起app 2 lat temu
plugins ab8e0706eb feat(callapp): 2 lat temu
schemes 86771aabf0 feat(login): upd 3 lat temu
static aa3bd9aa9e Merge branch 'nuxt' into dev-5.3.1 2 lat temu
store a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
.editorconfig 0fbcfe1211 fix(推流广告): 修改方案 3 lat temu
.env.development 17ed295b18 feat(env): 修改文件中心访问地址 2 lat temu
.env.production 17ed295b18 feat(env): 修改文件中心访问地址 2 lat temu
.env.staging 17ed295b18 feat(env): 修改文件中心访问地址 2 lat temu
.env.test 17ed295b18 feat(env): 修改文件中心访问地址 2 lat temu
.eslintignore a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
.eslintrc.js 899ca5d5df feat(nuxt): vant有个bug更换为vuetify 3 lat temu
.gitignore 0e4e679991 chore(nuxt): upd 3 lat temu
.npmrc f7c914a527 chore(nuxt): upd 3 lat temu
.prettierignore a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
.prettierrc 0fbcfe1211 fix(推流广告): 修改方案 3 lat temu
.stylelintignore a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
README.md a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
jsconfig.json a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
nuxt.config.js e1e5fcdee9 feat(callapp): 测试唤起app 2 lat temu
package-lock.json e1e5fcdee9 feat(callapp): 测试唤起app 2 lat temu
package.json e1e5fcdee9 feat(callapp): 测试唤起app 2 lat temu
pnpm-lock.yaml a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu
stylelint.config.js a0e8122281 chore(nuxt): 项目转移到nuxt 3 lat temu

README.md

android-cloud-H5-nuxt

部分环境变量含义

process.env.NODE_ENV

打包模式 两种模式 development 表示开发模式 production 表示发布模式

process.env.MODE

服务器环境 四个环境 development 开发环境 test 测试环境 staging 验收环境 production 生产环境

Build Setup

# install dependencies
$ npm install

# serve with hot reload at localhost:3000
$ npm run dev

# build for production and launch server
$ npm run build
$ npm run start

# generate static project
$ npm run generate

For detailed explanation on how things work, check out the documentation.

Special Directories

You can create the following extra directories, some of which have special behaviors. Only pages is required; you can delete them if you don't want to use their functionality.

assets

The assets directory contains your uncompiled assets such as Stylus or Sass files, images, or fonts.

More information about the usage of this directory in the documentation.

components

The components directory contains your Vue.js components. Components make up the different parts of your page and can be reused and imported into your pages, layouts and even other components.

More information about the usage of this directory in the documentation.

layouts

Layouts are a great help when you want to change the look and feel of your Nuxt app, whether you want to include a sidebar or have distinct layouts for mobile and desktop.

More information about the usage of this directory in the documentation.

pages

This directory contains your application views and routes. Nuxt will read all the *.vue files inside this directory and setup Vue Router automatically.

More information about the usage of this directory in the documentation.

plugins

The plugins directory contains JavaScript plugins that you want to run before instantiating the root Vue.js Application. This is the place to add Vue plugins and to inject functions or constants. Every time you need to use Vue.use(), you should create a file in plugins/ and add its path to plugins in nuxt.config.js.

More information about the usage of this directory in the documentation.

static

This directory contains your static files. Each file inside this directory is mapped to /.

Example: /static/robots.txt is mapped as /robots.txt.

More information about the usage of this directory in the documentation.

store

This directory contains your Vuex store files. Creating a file in this directory automatically activates Vuex.

More information about the usage of this directory in the documentation.