Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugs logs #551

Closed
wants to merge 22 commits into from
Closed

Debugs logs #551

wants to merge 22 commits into from

Conversation

axentiatech
Copy link

No description provided.

iamabhaymittal and others added 22 commits February 25, 2025 13:02
Add comprehensive path aliases for various project directories, improving import resolution and code organization. Utilize Node.js path utilities to dynamically generate aliases for different source code directories.
Update tsconfig.json to streamline configuration:
- Change moduleResolution from "Bundler" to "node"
- Simplify path alias for "@/*" to use "src/*"
- Remove commented sections and unused include paths
- Add detailed logging for NextAuth callbacks and events
- Implement custom signIn, redirect, session, and jwt callbacks
- Add global error handler for NextAuth errors
- Update GoogleProvider with additional authorization parameters and profile transformation
- Enhance SignUpForm with logging for form submission and Google sign-in process
- Ensure environment variables are used for Google client configuration
- Update various package dependencies in `package.json` and `pnpm-lock.yaml`.
- Modify `email:dev` script in `package.json`.
- Add new dependencies and remove unused ones.
- Update `@prisma/client`, `@prisma/generator-helper`, `@remixicon/react`, `sharp`, and other package versions.
- Update `@radix-ui` packages to use new React type definitions.
- Upgrade `@tiptap` packages to latest versions.
- Include new packages such as `@babel/runtime` and `@floating-ui`.
- Update `@types` packages for React and other libraries.
feat(signin): add detailed logging for sign-in process and error handling

feat(signup): add detailed logging for Google sign-up process

feat(middleware): add CORS headers and debug header to middleware response

feat(trpc): enhance query client with retry logic and logging for fetch requests

chore(shared): improve URL determination with logging and fallbacks
Copy link

Hey @axentiatech thank you for opening this pull request! 👋

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Debugs logs". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@dahal
Copy link
Contributor

dahal commented Feb 27, 2025

Why all these console logs @axentiatech @iamabhaymittal ?

@dahal dahal closed this Feb 27, 2025
@iamabhaymittal
Copy link

hey @dahal sorry this PR raise was a mistake.

also, i've been trying to get this deployed and hosted on vercel, anyway you can help me with this? i added all those loggers to see what's going on in the backend. it just won't work on vercel, none of the buttons

@dahal
Copy link
Contributor

dahal commented Feb 27, 2025

It's mostly configured to be self-deployed using docker, and captable is still work in progress, and is not production ready. It cannot be deployed to vercel and it won't work there because it currently uses pg-boss to process postgress queues.

@iamabhaymittal
Copy link

Thanks so much for the reply @dahal , really appreciate the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants