/**
 * Whether remote debugging is enabled. Toggled by the `remote` user setting or the
 * `NEEDLE_REMOTE` env var (the env var wins so you can flip it without editing the
 * config: `NEEDLE_REMOTE=1 npm run dev`, or `NEEDLE_REMOTE=false` to force off).
 * @param {import('../types/userconfig.js').userSettings} [userSettings]
 * @returns {boolean}
 */
export function isRemoteEnabled(userSettings?: import("../types/userconfig.js").userSettings): boolean;
/**
 * Remote debugging plugin.
 *
 * Binds the Vite dev server to the LAN (`server.host = true`) so other devices can
 * reach it, and prints the network URL + a scannable QR code once the server is
 * listening. HTTPS itself is provided by `@vitejs/plugin-basic-ssl`, which
 * {@link needlePlugins} adds to the plugin array when remote is enabled (WebXR and
 * other secure‑context features on the device require https).
 *
 * The page's console / errors / device info already stream back to the dev server
 * via the Needle logger (`needleLogger` + `logger.client.js`) over Vite's
 * websocket, landing in `node_modules/.needle/logs/latest.client.needle.log`. This
 * plugin is read‑only: it does not (yet) inject commands back into the page.
 *
 * @param {"build" | "serve" | undefined} command
 * @param {unknown} _config
 * @param {import('../types/userconfig.js').userSettings} [userSettings]
 * @returns {import('vite').Plugin | null}
 */
export function needleRemote(command: "build" | "serve" | undefined, _config: unknown, userSettings?: import("../types/userconfig.js").userSettings): import("vite").Plugin | null;