fix(ui): app footer layout and build environment on narrow screens

[userquin]

Footer links on narrow screens displayed below the build info.

This PR just moves the BuildEnvironment.vue after links container updating its styles to add some margins:

• added test for both, AppFooter.vue and BuildEnvironment.vue: from root run vite test --project nuxt -t BuildEnvironment

I haven't found a way to mock useAppConfig => small refactor at BuildEnvironment.vue to accept BuildInfo and updated modules/build-env.ts to mock it (maybe using useRuntimeConfig().public instead ? ).

supersedes #963

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Feb 8, 2026 11:16pm
npmx.dev	Ready	Preview, Comment	Feb 8, 2026 11:16pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Feb 8, 2026 11:16pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR moves the BuildEnvironment component within AppFooter.vue, changes its DOM placement and rendering order, and adjusts its footer-related responsive CSS classes. BuildEnvironment.vue now accepts an optional buildInfo prop and computes a fallback to appConfig.buildInfo. A new EnvType is introduced and BuildInfo.env is typed to EnvType. modules/build-env.ts is reworked to gate setup logic behind a TEST mode (producing synthetic BuildInfo) and to update runtime appConfig.env when fetching real values. New Vitest suites are added for AppFooter and BuildEnvironment to verify conditional rendering.

Suggested reviewers

• 43081j

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly relates to the changeset, describing the BuildEnvironment.vue relocation, style updates, test additions, and refactoring to accept BuildInfo prop.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# Search for TEST environment variable configuration
rg -n 'process\.env\.TEST|TEST\s*=' --type ts --type js --type json

Repository: npmx-dev/npmx.dev

Length of output: 112

---

🏁 Script executed:

# Check if std-env is in dependencies and availableif [ -f package.json ];thenecho"=== Checking package.json for std-env ==="
rg '"std-env"' package.json
echo""fi# Look for vitest configurationecho"=== Looking for vitest config files ==="
fd -e 'vitest\.config' -e 'vite\.config'2>/dev/null | head -20

Repository: npmx-dev/npmx.dev

Length of output: 168

---

🏁 Script executed:

# Search for vitest setup files and test configuration
rg -n 'TEST|test.*env' --type ts --type js vitest.config 2>/dev/null ||echo"No vitest.config found"

Repository: npmx-dev/npmx.dev

Length of output: 83

---

🏁 Script executed:

# Check if std-env is imported anywhere in the codebaseecho"=== Checking imports of std-env ==="
rg "from\s+['\"]std-env" --type ts --type js
echo""echo"=== Checking process.env.TEST usage across codebase ==="
rg "process\.env\.TEST" --type ts --type js -C 2

Repository: npmx-dev/npmx.dev

Length of output: 738

---

🏁 Script executed:

# Check NODE_ENV usage in test contextecho"=== Checking NODE_ENV usage ==="
rg "NODE_ENV\s*===\s*['\"]test" --type ts --type js
echo""echo"=== Checking test scripts in package.json ==="if [ -f package.json ];then
jq -r '.scripts | to_entries[] | select(.key | contains("test")) | "\(.key): \(.value)"' package.json 2>/dev/null || grep -A 5 '"test"' package.json
fi

Repository: npmx-dev/npmx.dev

Length of output: 615

---

Use isTest from std-env for consistent test-mode detection.

The process.env.TEST flag is not explicitly wired in this repository's test configuration. std-env (v3.10.0) is already available and isTest is already imported and used in modules/lunaria.ts, making this the standard approach. Replace process.env.TEST with isTest to ensure test-mode logic executes reliably.

-import { isCI } from 'std-env'+import { isCI, isTest } from 'std-env'
...
- if (process.env.TEST) {+ if (isTest) {

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	if(process.env.TEST){
	consttime=newDate()
	nuxt.options.appConfig.buildInfo={
	env,
	version: '0.0.0',
	commit: '704987bba88909f3782d792c224bde989569acb9',
	shortCommit: '704987b',
	branch: 'xxx',
	time: time.getTime(),
	privacyPolicyDate: time.toISOString(),
	}satisfiesBuildInfo
	}else{
	const[{env: useEnv, commit, shortCommit, branch },privacyPolicyDate]=awaitPromise.all([
	getEnv(nuxt.options.dev),
	getFileLastUpdated('app/pages/privacy.vue'),
	])
	env=useEnv
	nuxt.options.appConfig.env=useEnv
	if(isTest){
	consttime=newDate()
	nuxt.options.appConfig.buildInfo={
	env,
	version: '0.0.0',
	commit: '704987bba88909f3782d792c224bde989569acb9',
	shortCommit: '704987b',
	branch: 'xxx',
	time: time.getTime(),
	privacyPolicyDate: time.toISOString(),
	}satisfiesBuildInfo
	}else{
	const[{env: useEnv, commit, shortCommit, branch },privacyPolicyDate]=awaitPromise.all([
	getEnv(nuxt.options.dev),
	getFileLastUpdated('app/pages/privacy.vue'),
	])
	env=useEnv
	nuxt.options.appConfig.env=useEnv