Skip to content

ban12-project/ban12-site

Repository files navigation

Ban12.com projects

This is ban12.com all website source code

What's inside?

This projects includes the following packages/apps:

Apps and Packages

  • web: ban12
  • blog: a blog app with Tailwind CSS
  • shortcuts: the app for sharing shortcuts access online here
  • i18n: minimal i18n routing and translations
  • ui: a stub React component library with Tailwind CSS shared by both web and blog applications
  • @repo/eslint-config: eslint configurations (includes eslint-config-next and eslint-config-prettier)
  • @repo/tailwind-config: tailwind.config.tss used throughout the monorepo
  • @repo/typescript-config: tsconfig.jsons used throughout the monorepo

Each package/app is 100% TypeScript.

Building packages/ui

This example is set up to produce compiled styles for ui components into the dist directory. The component .tsx files are consumed by the Next.js apps directly using transpilePackages in next.config.js. This was chosen for several reasons:

  • Make sharing one tailwind.config.js to apps and packages as easy as possible.
  • Make package compilation simple by only depending on the Next.js Compiler and tailwindcss.
  • Ensure Tailwind classes do not overwrite each other. The ui package uses a ui- prefix for it's classes.
  • Maintain clear package export boundaries.

Another option is to consume packages/ui directly from source without building. If using this option, you will need to update the tailwind.config.js in your apps to be aware of your package locations, so it can find all usages of the tailwindcss class names for CSS compilation.

For example, in tailwind.config.js:

  content: [
    // app content
    `src/**/*.{js,ts,jsx,tsx}`,
    // include packages if not transpiling
    "../../packages/ui/*.{js,ts,jsx,tsx}",
  ],

If you choose this strategy, you can remove the tailwindcss and autoprefixer dependencies from the ui package.

Utilities

This Turborepo has some additional tools already setup for you:

Releases

No releases published

Packages

No packages published