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

it does not change the newly cloned directory #19

Open
coolpraz opened this issue Oct 22, 2024 · 0 comments · May be fixed by #24
Open

it does not change the newly cloned directory #19

coolpraz opened this issue Oct 22, 2024 · 0 comments · May be fixed by #24
Labels
bug Something isn't working

Comments

@coolpraz
Copy link

Environment

System:
OS: macOS 13.7
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 481.00 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.10.0 - /usr/local/bin/node
Yarn: 1.22.21 - /usr/local/bin/yarn
npm: 10.2.5 - /usr/local/bin/npm
Browsers:
Brave Browser: 124.1.65.123
Chrome: 130.0.6723.58
Safari: 18.0.1

Describe the issue

when executing command npx auth init --example command did not change directory to the new project and produce error message.

npx auth init --example
? Select a framework Next.js (next)
? Name of the project test
Cloning into 'test'...
? Initiailze .env with `AUTH_SECRET` yes
📝 Created /Users/coolpraz/Code/test123/test/.env.local with `AUTH_SECRET`.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /Users/coolpraz/Code/test123/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/Users/coolpraz/Code/test123/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in: /Users/coolpraz/.npm/_logs/2024-10-22T17_47_52_258Z-debug-0.log

How to reproduce

npx auth init --example

Expected behavior

scaffhold new nextjs application with new auth.js

@coolpraz coolpraz added the bug Something isn't working label Oct 22, 2024
@odeta939 odeta939 linked a pull request Feb 5, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant