-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Next.js Commerce boilerplates for each provider #347
Comments
it will be great also if we can remove other unused providers without breaking anything |
It seems to be in progress, see #252 |
Closing it as it's not really an issue |
Should probably reopen and tag a contributor? because the problem has not been solved with #252, where we are still forced to keep all provider framework code when we really just need 1 provider. |
I think it's big mistake and seem like not yet already for production. |
Everyone might need a way to start a new Next.js Commerce app with a single provider, without all the references to providers that won't be used, and also without the demo layout. Is there any solution for this on the roadmaps?
Here are some ideas as I'm not sure on how would be the best way to handle it:
create-next-app
or to a new CLI likecreate-next-commerce
with a option-p [name]
/--provider [name]
bigcommerce
andshopify
branches, but I'm not sure if it's updated/being used for this purposeThe text was updated successfully, but these errors were encountered: