You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On inspection, this is a typo which should read App directory doesn't exist
A deeper issue, though, is that I don't expect the app dir to pre-exist. I'm expecting the code mod to create it, because I am expecting this upgrade to move from pages dir to app dir along with the rest of the upgrade.
Paste all your error logs here:
PASTE_HERE (leave the ``` marks)
Paste all relevant code snippets here:
PASTE_HERE (leave the ``` marks)
What are detailed steps to reproduce this?
Run blitz -v and paste the output here:
PASTE_HERE (leave the ``` marks)
Please include below any other applicable logs and screenshots that show your problem:
No response
The text was updated successfully, but these errors were encountered:
if i have next.config.js instead of blitz.config.js the codemod unnecessarily errors
it errors if i don't have an app dir. maybe this is proper? but can it just make an app dir?
it errors after inserting import { withBlitz } from "app/blitz-client"; blindly, if it was already in the file under insertion; instead, the mod should check ahead of time and only insert if needed
What is the problem?
when i run
npx @blitzjs/codemod upgrade-legacy
as instructed in https://blitzjs.com/docs/upgrading-from-framework, I see an error:App directory doesn't exit
On inspection, this is a typo which should read
App directory doesn't exist
A deeper issue, though, is that I don't expect the app dir to pre-exist. I'm expecting the code mod to create it, because I am expecting this upgrade to move from pages dir to app dir along with the rest of the upgrade.
Paste all your error logs here:
Paste all relevant code snippets here:
What are detailed steps to reproduce this?
Run
blitz -v
and paste the output here:Please include below any other applicable logs and screenshots that show your problem:
No response
The text was updated successfully, but these errors were encountered: