rioam2 / starter-firebase-nextjs Goto Github PK

Add support for automating setup by giving an option to create firebase projects for production and staging environments seperately

Due to lack of testing on projects without a staging environment setup, CI/CD tests fail when preview:staging is called. Tests should point to preview:production server when no Staging environment is setup.

Add chai for assertions and possibly mocha for unit/functional testing and cypress for integration testing...

Tests should be run before commits are signed/pushed. Use Husky to test only staged/indexed files using git stash --keep-index.

Additionally, all files should be linted to maintain consistent code style.

Directories for unit tests and integration tests should be consolidated under a common tests/directory in the repository root.

Because of how merging will be managed, it will be beneficial to have package.json sorted by key before every commit. This can be done with the sort-package-json package from npm. Adding this as a development dependency is a sufficient alternative to using npx. Husky should be used to sort keys before each commit made.

Similar to how forked repositories work, update child clones/instances of this template repository with updated commits using git cherry-picking.

I have developed a separate tool for this, git-upstream-template, which should handle merging details and the overall interface.

git-upstream-template should be implemented to keep child clones/instances up-to-date/even with this repository.