This project is a template nuxt3 project.
The minimum required functions are implemented as a template project and the essentials are explained. This project also implement unit testing, E2E testing, and analyzing source code by SonarQube.
This project implement the following.
- Vitest (unit test)
- EsLint
- VeeValidate
- Navigation guard
- Pinia
- Puppeteer (E2E test)
- SonarQube
- TypeScript
- Create New Project
- Typescript Setup
- EsLint Setup with Typescript
- Vitest Setup
- VeeValidate Setup
- VeeValidate Testing
- Navigation guard
- Pinia Setup
- Pinia Testing
- Data Fetching
- E2E Testing By Puppeteer
- Analyzing source code by SonarQube
Create New Project
Run below command to create a new nuxt3 project.
npx nuxi init <project-name>
If you want to change source directory, add the following to nuxt.config.ts.
// nuxt.config.ts
export default defineNuxtConfig({
srcDir: 'src/'
});
npm install
npm run dev
You can access http://localhost:3000 to use this application.
Typescript Setup
# install Typescript
npm install --save-dev typescript vue-tsc @types/node
Add typescript to nuxt.config.ts.
// nuxt.config.ts
export default defineNuxtConfig({
typescript: {
shim: false, // Generate shims file(If you use Volar in VSCode, set false)
strict: true, // Enable strict mode
typeCheck: true // When run nuxt dev or nuxt build, run type check at the same time
},
});
EsLint Setup with Typescript
# install ESlint
npm install --save-dev @nuxtjs/eslint-config-typescript eslint
Create .eslintrc in root directory and add the following to .eslintrc.
{
"extends": [
"@nuxtjs/eslint-config-typescript"
]
}
Add the following item to scripts in package.json.
{
"scripts": {
"lint": "eslint --ext \".js,.ts,.vue\" --ignore-path .gitignore .",
"lint:fix": "npm run lint -- --fix"
}
}
Use below command to run ESLint.
# run ESLint
npm run lint
# run ESLint + fix code
npm run lint:fix
Vitest Setup
# install Vitest
npm install --save-dev vitest @testing-library/vue happy-dom
Create vitest.config.ts in root directory and add the following to vitest.config.ts.
// vitest.config.ts
import path from 'path'
import { defineConfig } from 'vitest/config'
import Vue from '@vitejs/plugin-vue'
import AutoImport from 'unplugin-auto-import/vite'
export default defineConfig({
resolve: {
alias: {
'~': path.resolve(__dirname, './src'),
'@': path.resolve(__dirname, './src')
}
},
test: {
globals: true,
environment: 'happy-dom'
}
})
Add the following to package.json.
{
"config": {
"path": "./src/tests/unitTest/pages/index.spec.ts"
},
"scripts": {
"test:all": "vitest",
"test:linux": "vitest $npm_package_config_path",
"test:win": "vitest %npm_package_config_path%"
},
}
Use below plugin because vitest does not import function that auto import by Nuxt.
# https://github.com/antfu/unplugin-auto-import
npm install --save-dev unplugin-auto-import
Add plugins to vitest.config.ts
// vitest.config.ts
export default defineConfig({
plugins: [
Vue(),
AutoImport({
// Set plugin name you want to import. You can set preset name.
// https://github.com/antfu/unplugin-auto-import/tree/main/src/presets
imports: ['vue', 'pinia', 'vue-router']
})
],
})
You can set custom plugin like this.
// vitest.config.ts
AutoImport({
imports: [
{
"nuxt/app": [
"foo"
]
}
]
})
npm install --save-dev @vitest/coverage-c8 vitest-sonar-reporter
Add the following to vitest.config.ts.
// vitest.config.ts
export default defineConfig({
test: {
coverage: {
provider: 'c8',
include: ['src/**/*.{vue,js,ts}'],
all: true,
reporter: ['html', 'clover', 'text']
},
root: '.',
reporters: ['verbose', 'vitest-sonar-reporter'],
outputFile: 'test-report.xml'
}
});
Add --coverage to the following item in package.json.
{
"scripts": {
"test:all": "vitest --coverage",
"test:linux": "vitest --coverage $npm_package_config_path",
"test:win": "vitest --coverage %npm_package_config_path%"
},
}
Add index.vue to pages directory.
// index.vue
<template>
<h1 data-testid="page-title">
Pages/index.vue
</h1>
</template>
Here is a test code of index.vue.
import { describe, expect, test } from 'vitest'
import { render } from '@testing-library/vue'
import Index from '~/pages/index.vue'
describe('Index', () => {
test('Index page should render page title', () => {
// Arrange
const { container } = render(Index)
// You need to call trim() because textContent return text with spaces added back and forth.
const title = container.querySelector('[data-testid="page-title"]')?.textContent?.trim()
// Assert
expect(title).toBe('Pages/index.vue')
})
})
Run below command to run test.
# run all tests
npm run test:all
You can also run each test file. Set test file path to config:path in package.json.
{
"config": {
"path": "./src/tests/unitTest/pages/index.spec.ts"
},
}
# Run test file defined config:path in package.json (Mac/Linux)
npm run test:linux
# Run test file defined config:path in package.json (Windows)
npm run test:win
VeeValidate Setup
# install VeeValidate
npm install --save-dev vee-validate @vee-validate/i18n @vee-validate/rules
Create vee-validate-plugin.ts in root directory and add the following to vee-validate-plugin.ts.
// vee-validate-plugin.ts
import { localize } from '@vee-validate/i18n'
import en from '@vee-validate/i18n/dist/locale/en.json'
import AllRules from '@vee-validate/rules'
import { defineRule, configure } from 'vee-validate'
import { defineNuxtPlugin } from '#app'
export default defineNuxtPlugin((_nuxtApp) => {
configure({
generateMessage: localize({
en
})
})
Object.keys(AllRules).forEach((rule) => {
// import all rules
defineRule(rule, AllRules[rule])
})
})
In vee-validate4, there are two ways to implement validation.
- implement validation in script setup
- implement validation in html
If you implement validation in script setup, use useForm/useField.
<script lang="ts" setup>
import { useForm, useField } from 'vee-validate'
// Form configuration. See the following for more details.
// https://vee-validate.logaretm.com/v4/api/use-form/#api-reference
const { handleSubmit, errors, isSubmitting, meta } = useForm({
// Set validation rule
validationSchema: {
email: 'required|email'
}
})
// Field configuration
const { value: email } = useField('email')
// If you click submit button, this function called.
const foo = () => {
console.log(email.value)
}
// If you click submit button, this function called and also run validation check at the same time.
const foo = handleSubmit(() => {
console.log(email.value)
})
</script>
<template>
<input v-model="email" type="text" name="email">
<!-- Show error message -->
<span v-if="errors.email">{{ errors.email }}</span>
<!-- When all field value is valid, meta.valid return true. -->
<button type="button" :disabled="!meta.valid" @click="foo">Submit</button>
<!-- If the form submission function is being run, isSubmitting return true. -->
<button type="button" :disabled="isSubmitting" @click="foo">Submit</button>
</template>
If you implement validation in html, use Form/Field components.
<script lang="ts" setup>
import { Form, Field, ErrorMessage } from 'vee-validate'
// If you click submit button, this function called.
const foo = (values: Record<string, any>) => {
console.log(values.email)
}
</script>
<template>
<!-- Form configuration. See the following for more details -->
<!-- https://vee-validate.logaretm.com/v4/api/use-form/#api-reference -->
<Form v-slot="{ meta, isSubmitting }" data-testid="validation-form" @submit="foo">
<Field rules="required|email" name="email" as="input" type="text" />
<!-- Show error message -->
<ErrorMessage name="email" />
<!-- When all field value is valid, meta.valid return true. -->
<button :disabled="!meta.valid">Submit</button>
<!-- If the form submission function is being run, isSubmitting return true. -->
<button :disabled="isSubmitting">Submit</button>
</Form>
</template>
VeeValidate Testing
# flush-promises install
npm install --save-dev flush-promises
To import vee-validate configuration, add setupFiles to vitest.config.ts.
// vitest.config.ts
export default defineConfig({
test: {
// Import below file when run test.
setupFiles: './src/tests/unitTest/setup.ts'
}
})
Create setup.ts in src/tests/unitTest and add the following to setup.ts.
// setup.ts
import { localize } from '@vee-validate/i18n'
import en from '@vee-validate/i18n/dist/locale/en.json'
import AllRules from '@vee-validate/rules'
import { defineRule, configure } from 'vee-validate'
import { vi } from 'vitest'
import flushPromises from 'flush-promises'
// vee-validate setup
configure({
generateMessage: localize({
en
})
})
Object.keys(AllRules).forEach((rule) => {
// import all rules
defineRule(rule, AllRules[rule])
})
// Call this method after you called fireEvent.
// After call this method, your fireEvent operation will apply to HTML.
export const waitPerfectly = async () => {
await flushPromises()
vi.runAllTimers()
await flushPromises()
}
Here is a sample test code of form validation. It tests email format.
See the following for more details.
- https://vee-validate.logaretm.com/v4/guide/testing
- https://github.com/testing-library/vue-testing-library/blob/main/src/__tests__/validate-plugin.js
// form.vue
<script lang="ts" setup>
import { Form, Field, ErrorMessage } from 'vee-validate'
const foo = (values: Record<string, any>) => {
console.log(values.email)
}
</script>
<template>
<Form v-slot="{ meta, isSubmitting }" data-testid="validation-form" @submit="foo">
<Field rules="required|email" name="email" as="input" type="text" data-testid="input-email" />
<ErrorMessage name="email" data-testid="email-error-msg" />
<button :disabled="!meta.valid">Submit</button>
</Form>
</template>
// form.spec.ts
import { describe, expect, test, vi } from 'vitest'
import { fireEvent, render } from '@testing-library/vue'
import { waitPerfectly } from '../setup'
import Form from '~/pages/form.vue'
vi.useFakeTimers()
test('the email field should be a valid email', async () => {
// Arrange
const { container } = render(Form)
const inputElement = container.querySelector('[data-testid="input-email"]') as HTMLInputElement
// Act
// Input a invalid value
await fireEvent.update(inputElement, 'abc')
await fireEvent.blur(inputElement)
// Apply html
await waitPerfectly()
// Get error message
const errorMsg = container.querySelector('[data-testid="email-error-msg"]')?.textContent
// Assert
expect(errorMsg).toBe('The email field must be a valid email')
})
You can implement redirect function in middleware directory.
The file have different functions by setting the the following file name.
- redirect.ts (anonymous (or inline) route middleware, which are defined directly in the pages where they are used.)
// foo.vue
<script setup>
definePageMeta({
middleware: ["redirect"]
})
</script>
- redirect.global.ts (automatically run on every route change)
Here is a sample code. See this for more details.
// redirect.global.ts
export default defineNuxtRouteMiddleware((to, from) => {
// If you access /
if (to.path === '/') {
// Redirect to login
return navigateTo('login')
}
})
See this for test implementation .
Pinia Setup
# install Pinia
npm install pinia @pinia/nuxt
If you're using npm, you might encounter an ERESOLVE unable to resolve dependency tree error. In that case, add the the following to your package.json:
{
"overrides": {
"vue": "latest"
}
}
If you see below error message, fix override:vue like below.
npm ERR! Invalid comparator: latest
{
"overrides": {
"vue": "3.2.45"
}
}
Add the following to nuxt.config.ts
// nuxt.config.ts
export default defineNuxtConfig({
modules: [
['@pinia/nuxt',
{
autoImports: [
// Import defineStore
'defineStore'
]
// If you use vuex at the same time, add the following
// disableVuex: false
}
]
]
});
Create user.ts in store directory and add the following to user.ts.
// user.ts
// If you add defineStore to autoImports in nuxt.config.ts, you don't need to import below
import { defineStore } from 'pinia'
export const useUserStore = defineStore('user', {
state: () => ({
// User definition and initialization
user: { email: '', password: '' }
}),
actions: {
// Update use info
setUserInfo (email: string, password: string) {
this.user.email = email
this.user.password = password
}
}
})
Here is a sample code using store from vue file.
// store.vue
<script lang="ts" setup>
import { useUserStore } from '../store/user'
// Use store
const store = useUserStore()
// Get email from store user info
const email = store.user.email
// Get password from store user info
const password = store.user.password
// Update store user info
store.setUserInfo("new email", "new password")
</script>
Pinia Testing
# install @pinia/testing
npm install --save-dev @pinia/testing
When run test file using pinia, the following error occurs.
getActivePinia was called with no active Pinia. Did you forget to install pinia?
To avoid this error, add the following to beforeEach.
import { setActivePinia, createPinia } from 'pinia'
beforeEach(() => {
setActivePinia(createPinia())
})
You can set the initial state of all of your stores when creating a testing pinia by passing an initialState. See this for more details.
import { beforeEach, test } from 'vitest'
import { render } from '@testing-library/vue'
import { setActivePinia, createPinia } from 'pinia'
import { createTestingPinia } from '@pinia/testing'
import Foo from '~/pages/foo.vue'
beforeEach(() => {
setActivePinia(createPinia())
})
test('store user info should set the initial value', () => {
// Arrange
const { container } = render(Foo, {
global: {
plugins: [
createTestingPinia({
initialState: {
user: { user: { email: 'Initial email', password: 'Initial password' } }
}
})
]
}
})
})
Nuxt provides useFetch instead of axios. It handles data fetching within your application. See this for more details.
// api.vue
<script lang="ts" setup>
const { data: bar } = await useFetch('/api/v1/foo')
</script>
<template>
Result: {{ bar }}
</template>
E2E Testing By Puppeteer
Most things that you can do manually in the browser can be done using Puppeteer as E2E testing.
# install Puppeteer
npm install --save-dev puppeteer
Here is a sample E2E testing code. It tests submit button state.
import { afterAll, beforeAll, describe, expect, test } from 'vitest'
import { launch, PuppeteerLaunchOptions } from 'puppeteer'
import type { Browser, Page } from 'puppeteer'
// Set browser launch option. See the following for more details.
// https://pptr.dev/api/puppeteer.browserlaunchargumentoptions
const options: PuppeteerLaunchOptions = {
headless: false,
slowMo: 75,
defaultViewport: {
width: 1280,
height: 1024
},
devtools: true,
args: ['--window-size=1680,1024']
}
describe('E2E', () => {
let browser: Browser
let page: Page
beforeAll(async () => {
browser = await launch(options)
page = await browser.newPage()
})
afterAll(async () => {
await browser.close()
})
test('1-If you input a valid value, submit button should enable', async () => {
try {
// Arrange
await page.goto('http://localhost:3000/foo')
// Act
// Input email
await page.type('input[name="email"]', '[email protected]')
// Input password
await page.type('input[name="password"]', 'foo')
// Get submit button state. inactive → true, active → false
const isDisabled = await page.$eval(
'[data-testid="submit-btn"]',
element => (element as HTMLButtonElement).disabled
)
// Take a screenshot
await page.screenshot({
path: './src/tests/e2eTest/evidence/pages/foo/test-01.png',
fullPage: true
})
// Assert
expect(isDisabled).toBeFalsy()
} catch (e) {
console.error(e)
expect(e).toBeUndefined()
}
}, 60000)
})
To run E2E testing, add the test file path to config:path in package.json.
{
"config": {
"path": "./src/tests/e2eTest/spec/foo.spec.ts"
},
}
# run application server
npm run dev
# run E2E testing (Linux/Mac)
npm run test:linux
# run E2E testing (Windows)
npm run test:win
Analyzing source code by SonarQube
SonarQube is a self-managed, automatic code review tool that systematically helps you deliver clean code.
# install SonarQube tools
npm install --save-dev sonarqube-scanner vitest-sonar-reporter
Add the following to vitest.config.ts.
- add lcov to reporter
- add reporters and outputFile to test
// vitest.config.ts
export default defineConfig({
test: {
coverage: {
// To collect coverage by SonarQube, add lcov.
reporter: ['html', 'clover', 'text', 'lcov']
},
// To analyze your test code by SonarQube, output test report file
reporters: ['verbose', 'vitest-sonar-reporter'],
outputFile: 'test-report.xml',
}
})
Create sonar-project.properties in root directory and add the following to sonar-project.properties. See this for more details.
sonar.projectKey=nuxt3-starter-guide
sonar.projectName=nuxt3-starter-guide
sonar.sources=src
sonar.tests=src/tests/
sonar.test.inclusions=src/tests/**/*.spec.ts
sonar.exclusions=**/*plugins*/**, src/tests/**/*.spec.ts, src/tests/**/setup.ts
sonar.testExecutionReportPaths=test-report.xml
sonar.javascript.file.suffixes=.js,.jsx
sonar.typescript.file.suffixes=.ts,.tsx,.vue
sonar.typescript.lcov.reportPaths=coverage/lcov.info
sonar.javascript.lcov.reportPaths=coverage/lcov.info
sonar.login=sqp_XXXXXXXXXXXXXXXXXXXXXX
Make sure you have installed SonarQube on your development machine. Run SonarQube server as localhost:9000 before do the following.
To create a SonarQube project, do the following.
-
Access the following url. http://localhost:9000/projects
-
Click [Create Project] and then click [Manually]
-
Input nuxt3-starter-guide in Project display name and Project key. Click [Set Up]
-
Click [Locally]
-
Click [Generate] and then generate project token
Add project token to sonar.login in sonar-project.properties. See this for more details of token.
sonar.login=sqp_XXXXXXXXXXXXXXXXXXXXXX
Add the following to scripts in package.json.
{
"scripts": {
"sonar": "sonar-scanner"
},
}
Run below command to run SonarQube analysis.
# run all tests
npm run test:all
# run SonarQube analysis
npm run sonar
You can access the following url to show result.