Unify service worker environment variable to NEXT_PUBLIC_ENABLE_SW_IN_DEV

[Copilot]

The service worker control used inconsistent environment variables: ENABLE_SW_IN_DEV in next.config.ts for build-time generation and NEXT_PUBLIC_ENABLE_SW_IN_DEV in sw-register.tsx for runtime registration. This required developers to set both variables.

Changes:

• next.config.ts: Changed from ENABLE_SW_IN_DEV to NEXT_PUBLIC_ENABLE_SW_IN_DEV for build-time SW generation control
• sw-register.tsx: Already used NEXT_PUBLIC_ENABLE_SW_IN_DEV for runtime registration (no change needed)
• Comments: Updated documentation in both files to reference the unified variable

Developers now set one variable to control both build-time and runtime behavior:

NEXT_PUBLIC_ENABLE_SW_IN_DEV=true npm run dev

The NEXT_PUBLIC_ prefix is required for client-side access in Next.js, and using it in next.config.ts (server-side) works correctly as all environment variables are available at build time.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This pull request unifies the environment variable used to control service worker behavior in development mode. Previously, the codebase used ENABLE_SW_IN_DEV in build-time configuration and NEXT_PUBLIC_ENABLE_SW_IN_DEV in runtime registration, requiring developers to set both variables. The PR standardizes on NEXT_PUBLIC_ENABLE_SW_IN_DEV for both contexts.

Changes:

• Updated next.config.ts to use NEXT_PUBLIC_ENABLE_SW_IN_DEV instead of ENABLE_SW_IN_DEV for build-time service worker generation control
• Updated comments in next.config.ts to reference the unified variable name
• Reformatted a logger call in sw-register.tsx for better readability (no functional change)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
next.config.ts	Changed environment variable from ENABLE_SW_IN_DEV to NEXT_PUBLIC_ENABLE_SW_IN_DEV and updated associated comments
src/components/sw-register.tsx	Reformatted multi-line logger.dev call for consistency (no functional changes)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The README.md file still references the old environment variable name ENABLE_SW_IN_DEV in lines 331, 334, and 337. Since this comment mentions that "This behavior should be documented in README.md," the documentation should be updated to use NEXT_PUBLIC_ENABLE_SW_IN_DEV to match the code changes and prevent confusion for developers.

Suggested change

	// To test PWA / offline functionality locally, start Next.js in development mode with NEXT_PUBLIC_ENABLE_SW_IN_DEV="true"
	// Example: NEXT_PUBLIC_ENABLE_SW_IN_DEV="true" npm run dev
	// This behavior should be documented in README.md for team members testing PWA features.
	// To test PWA / offline functionality locally, start Next.js in development mode with NEXT_PUBLIC_ENABLE_SW_IN_DEV="true".
	// Example: NEXT_PUBLIC_ENABLE_SW_IN_DEV="true" npm run dev
	// Set NEXT_PUBLIC_ENABLE_SW_IN_DEV only when you intentionally want to test PWA/offline behavior in development.