No push notifications

This is the no-op push option: nothing registers, no permission prompt ever appears, and there are no credentials to upload. It owns src/lib/push.ts as a re-export of the core shim, so @/lib/push keeps the same API whichever option you pick - push.usePushToken() returns { token: null, status: "unsupported" } and requestPermission() resolves false. Pick this until you actually have something to notify people about.

SetupCopy Anchor Link

bun run setup --push none

There's nothing to configure, no keys to paste, and no eas credentials to run.

When you want notifications, switch with bun run setup --push expo-notifications.

UsageCopy Anchor Link

The calls exist and are safe to write today, so screens don't need rewriting when you switch:

import { push } from "@/lib/push";

const { token, status } = push.usePushToken(); // always { token: null, status: "unsupported" }
const granted = await push.requestPermission(); // always false

GotchasCopy Anchor Link

• status is "unsupported", the same value the real module reports on web and simulators - so a screen that handles it correctly here handles those cases too.
• Nothing here needs a dev build; Expo Go is fine.

ReferenceCopy Anchor Link

Everything below is generated from modules/push/none/module.json - the same file bun run setup reads, so it is what actually lands in your repo.

InstallCopy Anchor Link

bun run setup --push none

Module id: push/none.

FilesCopy Anchor Link