Hi Kolby (and any other maintainers),
Thanks for creating and maintaining the next-supabase-stripe-starter – it looks like a great starting point!
I recently cloned the repository to start a new project. I noticed that the bun.lockb file is included in the main branch.
While the README heavily features bun commands (which is perfectly fine!), including a specific lock file (bun.lockb in this case) directly in a starter template repository can sometimes cause confusion or potential dependency resolution issues for users who might prefer or need to use npm or yarn.
Issue/Observation:
Cloning the repository includes bun.lockb.
Users without bun installed globally might try npm install or yarn install.
While npm install worked for me after an initial hiccup (where npm run dev failed because next wasn't found due to missing dependencies), the presence of bun.lockb could lead to ambiguity about the intended package manager or potential conflicts if different managers interpret dependencies differently without their own lock file generated first.
Suggestion:
Typically, starter templates or boilerplates omit package manager lock files (package-lock.json, yarn.lock, bun.lockb) to give the adopting user the flexibility to choose their preferred package manager and generate the appropriate lock file upon their first install. Lock files are more commonly committed in application repositories once development is underway.
Would you consider removing bun.lockb from the repository and adding *.lockb (or specifically bun.lockb) to the .gitignore file?
This would:
- Align with common practices for starter templates.
- Provide clarity and flexibility for users regarding package manager choice.
- Prevent potential (though perhaps minor) conflicts or confusion during the initial dependency installation process for non-bun users.
Thanks again for the great starter!
Hi Kolby (and any other maintainers),
Thanks for creating and maintaining the next-supabase-stripe-starter – it looks like a great starting point!
I recently cloned the repository to start a new project. I noticed that the bun.lockb file is included in the main branch.
While the README heavily features bun commands (which is perfectly fine!), including a specific lock file (bun.lockb in this case) directly in a starter template repository can sometimes cause confusion or potential dependency resolution issues for users who might prefer or need to use npm or yarn.
Issue/Observation:
Cloning the repository includes bun.lockb.
Users without bun installed globally might try npm install or yarn install.
While npm install worked for me after an initial hiccup (where npm run dev failed because next wasn't found due to missing dependencies), the presence of bun.lockb could lead to ambiguity about the intended package manager or potential conflicts if different managers interpret dependencies differently without their own lock file generated first.
Suggestion:
Typically, starter templates or boilerplates omit package manager lock files (package-lock.json, yarn.lock, bun.lockb) to give the adopting user the flexibility to choose their preferred package manager and generate the appropriate lock file upon their first install. Lock files are more commonly committed in application repositories once development is underway.
Would you consider removing bun.lockb from the repository and adding *.lockb (or specifically bun.lockb) to the .gitignore file?
This would:
Thanks again for the great starter!