A playground using Vite + React + TypeScript + TailwindCSS.
I'm always looking to improve as a developer and this playground is a way for me to try out new technology. The plan here is to continually build upon this playground so it's a fully-featured site with a bunch of cool stuff to play around with. Right now I am interested in:
- Modern state management solutions such as Recoil, Overmind, XState...
- TailwindCSS
- React with TypeScript
- SVG and Canvas
- Fun and interesting APIs
Vite is a fast frontend build tool. According to the README, it consists of two major parts:
- A dev server that serves your source files over native ES modules, with rich built-in features and astonishingly fast Hot Module Replacement (HMR).
- A build command that bundles your code with Rollup, pre-configured to output highly optimized static assets for production.
React is a JavaScript library for building user interfaces.
Due to its awesome renderer system, there are many React Renderor. So React can be not used only Web, for example, used by React Native.
Let's dive into React and Vite can use with React.
TypeScript is a superset of JavaScript. It is just one of NPM library, but it provides an original compiler.
When you use TypeScript with React, you can write JSX with TypeScript, called TSX. Then you can develop views written by Type-Safe template.
Tailwind CSS is modern utility-first CSS framework. It provides many CSS rules, but these are purged when production builds. So developers do not worry about CSS asset size for performance optimization.
In VSCode, I recommend to use intellisense extension.
Frequently, React developers are worried about how to write CSS in TSX(JSX) template. You must choose from CSS Modules, styled-components, linaria, and so on. Additionally, CSS architecture is difficult about scoping, e.g. BEM, FLOCSS.
When you decide to use Tailwind, you only write utility-first CSS classes, you don't have to worry about them!
Already set up ESLint and Prettier. You can customize the rules.
NOTICE: The template does not use eslint-plugin-prettier and prettier-eslint. So I recommend that running commands individually. e.g. prettier && eslint.
Please read: https://prettier.io/docs/en/integrating-with-linters.html.