Why use Website config?

One place for the lint and format settings of every Lupinum Nuxt website. Sites import two functions instead of copying config files, and Renovate rolls out every change as a normal dependency update.

Oxlint and oxfmt (through Vite+) check script code and format everything. ESLint checks only Vue <template> blocks, because oxlint cannot read them yet. The rules come from the Lupinum website handbook (standard F-07).

Requirements

• Node.js 22.14 or later, Node.js 24, or Node.js 26.

Installation

pnpm add -D @lupinum/website-config vite-plus eslint

Quick start

// vite.config.ts
import { defineConfig } from 'vite-plus'
import { lupinumVite } from '@lupinum/website-config'

export default defineConfig(lupinumVite())

// eslint.config.js
import { lupinumTemplateLint } from '@lupinum/website-config/eslint'

export default lupinumTemplateLint()

Use a coding agent

A coding agent is a development tool that can inspect and change your project.

Copy this task prompt into your application agent:

Use the installed @lupinum/website-config package to implement my requested feature.
Read the application's instructions first. Resolve @lupinum/website-config/agent-docs
from this application directory and read the relevant local pages.
Preserve the existing AGENTS.md. If it has no equivalent guidance, append
one short note to resolve installed package docs before integration work
and after dependency changes. Do not install a consumer skill.
Check the completed feature using this project's normal commands.

The installed documentation matches the package version. If an older version has no documentation export, use its README, types and matching release docs.

Documentation

Read the full documentation at website-config.lupinum.com.

Contributing

Read CONTRIBUTING.md. Run pnpm verify before you open a pull request.

Support and security

Ask questions in the Lupinum OSS Discord. Report vulnerabilities privately as described in SECURITY.md.

License

MIT © Lupinum OG.