fix: import.meta.ENV being undefined

[vinpogo]

No description provided.

[Copilot]

Pull request overview

This PR makes vuebugger more resilient in environments where import.meta.env may be missing, preventing runtime failures when the plugin/debug helper are loaded outside a Vite-style build.

Changes:

• Guard DebugPlugin.install behind import.meta.env?.DEV to avoid crashing when env is undefined.
• Guard debug() behind import.meta.env?.DEV for the same reason.
• Add a changeset to release a patch version of @vingy/vuebugger.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
packages/vuebugger/src/index.ts	Updates dev-only install guard to tolerate missing import.meta.env.
packages/vuebugger/src/debug.ts	Updates dev-only debug guard to tolerate missing import.meta.env.
.changeset/orange-towns-sing.md	Adds patch changeset describing the fix.

[Copilot]

Using optional chaining on import.meta.env?.DEV may prevent Vite from doing its usual static replacement / dead-code elimination for import.meta.env.DEV, which can cause the devtools code (and its imports) to remain in production bundles. Consider switching to a short-circuit guard that keeps a plain import.meta.env.DEV access (e.g., check import.meta.env first, then import.meta.env.DEV).

Suggested change

	if (!import.meta.env?.DEV) return
	if (!import.meta.env || !import.meta.env.DEV) return

[Copilot]

Using optional chaining on import.meta.env?.DEV may prevent Vite from statically replacing import.meta.env.DEV and applying dead-code elimination, leaving this debug path (and its imports) in production bundles. Prefer a guard that first checks import.meta.env exists but still references import.meta.env.DEV normally after that check.

Suggested change

	if (!import.meta.env?.DEV) return state
	if (
	typeof import.meta === 'undefined' ||
	!import.meta.env ||
	!import.meta.env.DEV
	) {
	return state
	}

[Copilot]

The changeset message says import.meta.ENV, but the actual property is import.meta.env (lowercase). Updating the text will make the release note accurate and easier to understand.

Suggested change

	fix: import.meta.ENV not being optional
	fix: import.meta.env not being optional