updates#179
Merged
Merged
Conversation
zakkiyyat
commented
Jun 15, 2026
zakkiyyat
commented
Contributor
- chore: scaffold monorepo foundation with shared and stellar packages
- feat(api): add modular monolith with auth and users modules
- feat(web): add Next.js login and registration pages
- feat(mobile): scaffold Expo React Native foundation
- docs: add CI workflows and foundation documentation
- fix: resolve lint, typecheck, and build issues across workspaces
Remove the existing product implementation (backend/mobile/web/legacy) on
this branch to start a clean hackathon-foundation monorepo using
apps/{api,web,mobile} and packages/{shared,stellar}, with workspace
tooling, prettier, and shared auth types/validation schemas.
Implement registration, login, JWT-based auth middleware, and a /me endpoint backed by MongoDB/Mongoose. Includes config validation, error handling, logging, and Vitest+Supertest tests running against an in-memory MongoDB instance.
Add AuthProvider for client-side auth state, a shared AuthForm using the @discoverly/shared validation schemas, and login/register pages with Vitest + Testing Library coverage for rendering and validation.
Add TypeScript, ESLint, Jest, and folder structure for components, screens, navigation, hooks, services, utils, and assets. No authentication or screens are implemented yet; this is setup-only, verified by a basic render test.
Add per-package GitHub Actions workflows (shared/stellar, api, web, mobile) replacing the old backend/mobile/web CI, and rewrite the root README plus docs/ with architecture, environment, testing, and contributor guides for the new monorepo foundation.
- Use a self-contained ESLint config for apps/web (eslint-config-next's bundled babel parser doesn't resolve correctly under npm workspaces) - Align apps/web on React 18 to avoid a duplicate React copy that broke Next's static error-page prerendering - Add @types/jest to apps/mobile for test file typechecking - Fix jsonwebtoken expiresIn typing in the auth service - Commit the root package-lock.json and ignore .next/tsbuildinfo output
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.