Go to file
fazli 0b18438a97 fix(notif+auth): camelCase badge fields, seller push prompt, only 401 signs out
- app/components/MyLayout.tsx / app/components/home/HomePageTopBar.tsx /
  app/routes/profile._index.tsx: the BadgeCounts type was declared with
  snake_case fields (order_updates, seller_orders) while the API's global
  camelCase renderer sends orderUpdates / sellerOrders on the wire — every
  read went to undefined, so the "buyer activity" dot on the profile icon
  and the order-badge on the store dashboard were silently stuck at 0.
  Fixed by renaming the interface to match the wire and adding sellerChat
  (per-store roll-up) so the store dashboard sidebar reads
  badges.sellerChat[storeId] instead of the buyer-side chat count.
- app/hooks/useBadgeCounts.ts: interface + EMPTY constant updated to
  camelCase + new sellerChat map.
- app/utils/api-error-handler.ts: 403 no longer force-redirects to /logout.
  It used to force-log-out on ANY 403/401, so an approved-but-unbadged
  owner (Ehsan / Noelabel) whose store dashboard fired the Instagram-tab
  query got a 403 → forced logout → the store page vanished mid-load
  and the seller landed on the home screen convinced they'd been kicked
  off their own store. Only 401 signs the session out now.
- app/components/store/StorePushPromptCard.tsx: new dashboard-level card
  that nudges the store owner/staff to enable browser push. Unlike the
  global buyer banner it's not dismissible-forever; "بعداً یادآوری کن"
  hides for 24h and it comes back until the user actually subscribes.
  Handles the permission="denied" path with an in-browser-settings hint.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-07-18 13:18:08 +00:00
app fix(notif+auth): camelCase badge fields, seller push prompt, only 401 signs out 2026-07-18 13:18:08 +00:00
docs first 2026-04-29 01:44:16 +03:30
k8s first 2026-04-29 01:44:16 +03:30
public feat(notifications): web push opt-in + unread nav badges 2026-06-17 14:02:56 +03:30
scripts first 2026-04-29 01:44:16 +03:30
src/api/types feat(chat): share the product into the chat + fix empty-thread preview 2026-07-13 15:09:01 +03:30
.dockerignore first 2026-04-29 01:44:16 +03:30
.env.development first 2026-04-29 01:44:16 +03:30
.env.example feat(address-map): MapLibre GL + Map.ir vector map & Persian reverse geocoding 2026-06-28 01:20:37 +03:30
.env.production first 2026-04-29 01:44:16 +03:30
.eslintrc.cjs first 2026-04-29 01:44:16 +03:30
.gitignore first 2026-04-29 01:44:16 +03:30
bun.lock first 2026-04-29 01:44:16 +03:30
components.json first 2026-04-29 01:44:16 +03:30
DEPLOYMENT.md first 2026-04-29 01:44:16 +03:30
docker-compose.yml first 2026-04-29 01:44:16 +03:30
Dockerfile first 2026-04-29 01:44:16 +03:30
Dockerfile.dev first 2026-04-29 01:44:16 +03:30
generate-types.ps1 first 2026-04-29 01:44:16 +03:30
generate-types.sh first 2026-04-29 01:44:16 +03:30
openapi-generator-cli.jar first 2026-04-29 01:44:16 +03:30
package-lock.json feat(address-map): MapLibre GL + Map.ir vector map & Persian reverse geocoding 2026-06-28 01:20:37 +03:30
package.json feat(address-map): MapLibre GL + Map.ir vector map & Persian reverse geocoding 2026-06-28 01:20:37 +03:30
postcss.config.js first 2026-04-29 01:44:16 +03:30
README.md first commit 2026-04-29 01:42:54 +03:30
tailwind.config.ts first 2026-04-29 01:44:16 +03:30
tsconfig.json first 2026-04-29 01:44:16 +03:30
vite.config.ts first 2026-04-29 01:44:16 +03:30

Welcome to Remix - yay!

Development

Run the dev server:

npm run dev

Deployment

First, build your app for production:

npm run build

Then run the app in production mode:

npm start

Now you'll need to pick a host to deploy it to.

DIY

If you're familiar with deploying Node applications, the built-in Remix app server is production-ready.

Make sure to deploy the output of npm run build

  • build/server
  • build/client

Styling

This template comes with Tailwind CSS already configured for a simple default starting experience. You can use whatever css framework you prefer. See the Vite docs on css for more information.