This project is created using next.js, typescript & scss with prepared configurations for dockerizing the project & release scripts with automatic changelog generation. local hooks for type-checking, testing & linting are also included which can be further configured, improved & reused in ci/cd pipelines.

The following schema is the main gist of the present project structure. Please follow the conventions in creating files & folders for keeping a unified, maintainable collaboration.

• __mocks__: mocks for node_modules
• public: static files
• src: source codes
  • mocks: mocks for components & utils
  • utils: custom hooks & helper functions
  • assets: scss styles, icons (svg, png, ...)
  • config: custom & general project configurations
  • routes: route files (slugs, paths, router, private routes, ...)
  • components: common components used everywhere
  • pages: pages (each folder in this directory presents a single page route entity which maps to a unique route/url)
  • views: views (page components)
    • SamplePage: a sample page
      • SamplePage.tsx: page component
      • SamplePage.module.scss: page styles
      • SamplePageService.ts: page services (api calls)
      • SamplePageViewModel.ts: page view model (states, actions, logic)
      • SamplePageTypes.ts: specific shared types for SamplePage & its components (optional)
      • SamplePage.md: page documentation (optional)
      • components: components specific to SamplePage
        • ComponentA: sample inner component (specific to this page) (if the component gets complicated, it can also have it's own service, viewModel & other layers)
          • ComponentA.tsx: component (atom)
          • ComponentA.module.scss: component's styles
          • ComponentA.test.tsx: component's tests
        • index.ts: barrel file for exporting ComponentA & other components in this directory
      • tests: test suites for the SamplePage main component, service & viewModel files
        • unit: unit test suites for SamplePage
          • SamplePageViewModel.unit.test.tsx
          • ...
        • integration: integration test suites for SamplePage
        • e2e: end-to-end test suites for SamplePage (using cypress)

# initialize husky hooks:
npm run init:husky

# start the dev server:
npm run dev

# test the project:
npm run cypress

# build for production:
npm run build

# build for bundle analysis:
npm run build-stats

# export static build as index.html:
npm run export

commits that do not follow the conventional config for standard-version will be rejected.

the following list is a gist of the available commit types:

build(scope?): description
chore(scope?): description
ci(scope?): description
docs(scope?): description
feat(scope?): description
fix(scope?): description
perf(scope?): description
refactor(scope?): description
revert(scope?): description
style(scope?): description
test(scope?): description

for more info, see: https://www.conventionalcommits.org/en/v1.0.0/

NOTE: any changes to these conventions should be synchronized with the standard-version configurations. Automatic versioning & changelog generation will suffer otherwise. We recommend staying with the default settings.

testing is done using cypress.

documentation is done using Markdown, JSDoc & TypeScript type declarations. the test files with proper descriptions can also be treated as a form of documentation.

# first release of the project (should run once forever):
npm run release:first
# for later releases use the following commands:
# semver pattern: `major.minor.patch` (e.g. `1.5.8`)
npm run release:patch
# or
npm run release:minor
# or
npm run release:major