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

mockBee 2.0: A Hub for CRA Templates #45

Closed
sohamsshah opened this issue Oct 29, 2021 · 0 comments · Fixed by #74
Closed

mockBee 2.0: A Hub for CRA Templates #45

sohamsshah opened this issue Oct 29, 2021 · 0 comments · Fixed by #74

Comments

@sohamsshah
Copy link
Contributor

sohamsshah commented Oct 29, 2021

Presently, users can install the mockBee backend-powered apps by create-mock-backend, but has few challenges:

  • The versions would soon get old with time. Need to maintain and keep all the apps with latest updates
  • These are technically CRA apps. But, if in future a new update for CRA is released; the present folder structure, approach or internal performance would get hindered.
  • mockBee is aimed to have tons of mock-backends. Maintenance is major drawback with current approach.

Proposed Solution:

  • Have individual package for each mockBee app and managed with package-manager such as lerna. Then, user should be able to install apps directly by npx create-react-app --template mockbee-social-media or similar approach. Also, if user wants, user can install by create-mock-backend and select their template which internally would do create-react-app --template selected-template.
  • This approach would ensure that all apps are in sync with latest CRA and users don't get confused about create-mock-backend to be a different thing as the aim to let users learn Frontend with simplicity.

This Issue will be actively looked into and very available to listen to views and opinions for improvements or better approaches.

Refer: https://create-react-app.dev/docs/custom-templates/

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.

1 participant