refactor: use t3 stack #300
Merged
Conversation
This file contains 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
and rm extraneous vscode files
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
and rm testing from blitz app and install husky at top level
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
and revert next config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #103
TODO: husky is broken on the t3 side and possibly on the blitz side. i'm using
--no-verifyfor now but we should fix it prior to mergeTODO: make an issue to remove LadderlyMigrationAdapter after prod is working on t3 for a month or so
we should be able to use the default of
adapter: PrismaAdapter(db) as Adapter,related https://claude.ai/chat/c50757e4-a0cb-4794-9a58-d2141222bdc0