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

Blitz new command won't generate a SQLite database #370

Closed
marraleks opened this issue Dec 8, 2021 · 1 comment · Fixed by blitz-js/blitz#3043
Closed

Blitz new command won't generate a SQLite database #370

marraleks opened this issue Dec 8, 2021 · 1 comment · Fixed by blitz-js/blitz#3043

Comments

@marraleks
Copy link

What is the problem?

When i run blitz new ... it's fails at Initializing SQLite database and I have to migrate manually after.

Paste all your error logs here:

✔ Retrieving the freshest of dependencies
✔ Resolving packages
✔ Fetching packages
✔ Linking dependencies
✔ Building fresh packages
✖ Initializing SQLite database.     <-- this
✔ Committing your app

Your new Blitz app is ready! Next steps:

   1. cd testapp
   2. blitz prisma migrate dev (when asked, you can name the migration anything).   <-- this
   3. blitz dev

Paste all relevant code snippets here:

blitz new ...

What are detailed steps to reproduce this?

  1. Run; blitz new ...

Run blitz -v and paste the output here:

blitz -v
macOS Big Sur | darwin-x64 | Node: v17.0.1

blitz: 0.44.3 (global)
blitz: undefined (local)

  Package manager: yarn
  System:
    OS: macOS 11.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 4.57 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v17.0.1/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: Not Found
    blitz: Not Found
    prisma: Not Found
    react: Not Found
    react-dom: Not Found
    typescript: Not Found


❯ blitz -v
macOS Big Sur | darwin-x64 | Node: v17.0.1

blitz: 0.44.3 (global)
blitz: undefined (local)

  Package manager: yarn
  System:
    OS: macOS 11.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 3.43 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v17.0.1/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: Not Found
    blitz: Not Found
    prisma: Not Found
    react: Not Found
    react-dom: Not Found
    typescript: Not Found

Please include below any other applicable logs and screenshots that show your problem:

No response

@alechp
Copy link

alechp commented Jan 4, 2022

Having the same issue

macOS Monterey | darwin-x64 | Node: v17.0.1

blitz: 0.44.4 (global)

  Package manager: npm 
  System:
    OS: macOS 12.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 1.46 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.0.1 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
    Watchman: 2021.11.15.00 - /usr/local/bin/watchman
  npmPackages:
    @prisma/client: Not Found
    blitz: Not Found
    prisma: Not Found
    react: Not Found
    react-dom: Not Found
    typescript: Not Found

First attempt

  1. Install npm install -g blitz
  2. Initialize new project (JS, fullstack app with auth, NPM, React Final Form)
  3. Receive sqlite error

Screen Shot 2022-01-04 at 2 11 30 PM

Second attempt

  1. Confirm sqlite exists, create explicit alias for sqlite to sqlite3 (grasping at straws)
  2. Uninstall blitz global (npm uninstall -g blitz) and re-install globally with yarn (yarn global add blitz)
  3. Changed from default shell (nu) to zsh (thought perhaps there was some weird env var issue)
  4. Created new project again (JS, fullstack app with auth, yarn, React Final Form)
  5. Received same initialization error

@itsdillon itsdillon transferred this issue from blitz-js/blitz Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants