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

Init fails, due to next.config not having the expected file extension. #186

Open
gaurangrshah opened this issue Apr 19, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gaurangrshah
Copy link

gaurangrshah commented Apr 19, 2024

Config File

{
  "hasSrc": true,
  "packages": [
    "shadcn-ui",
    "drizzle"
  ],
  "preferredPackageManager": "npm",
  "t3": false,
  "alias": "@",
  "analytics": true,
  "rootPath": "src/",
  "componentLib": "shadcn-ui",
  "driver": "sqlite",
  "provider": "turso",
  "orm": "drizzle"
}

Describe the bug
when running npx kirimase init the cli is unable to find a next.config.mjs file. I currently has a legacy dependency (contentlayer) in this project and because of it we are forced to use the .cjs extension instead.

To Reproduce
Steps to reproduce the behavior:

  1. Rename next.config.mjs to next.config.cjs
  2. Run npx kirimase init on the project root
  3. See error

Expected behavior
I hope that the cli would be robust enough to able to check to see if any next-config is available and apply the changes to that file regardless of the extension used in the project.

Screenshots
~image

Desktop (please complete the following information):

  • OS: macOS Sonoma
  • Browser: Arc

Additional context
n/a

@madebydor
Copy link

any fix?
I installed a fresh next application and I get this error

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

No branches or pull requests

3 participants