Components Library template with Vite, React and Storybook.
To publish your package, uncomment the necessary steps in the different .github/workflows/publish-*.yml files. It's also recommended to read this guide: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry
The PACKAGE_REGISTRY_TOKEN
secret is only needed when you need to install other private packages from your GitHub Packages registry,
which GITHUB_TOKEN
does not provide access to.
You'll also need to update .npmrc
, and remove publishConfig
from package.json
if you are publishing to NPM as a public package.
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:
- Configure the top-level
parserOptions
property like this:
export default tseslint.config({
languageOptions: {
// other options...
parserOptions: {
project: ["./tsconfig.node.json", "./tsconfig.app.json"],
tsconfigRootDir: import.meta.dirname,
},
},
});
- Replace
tseslint.configs.recommended
totseslint.configs.recommendedTypeChecked
ortseslint.configs.strictTypeChecked
- Optionally add
...tseslint.configs.stylisticTypeChecked
- Install eslint-plugin-react and update the config:
// eslint.config.js
import react from "eslint-plugin-react";
export default tseslint.config({
// Set the react version
settings: { react: { version: "18.3" } },
plugins: {
// Add the react plugin
react,
},
rules: {
// other rules...
// Enable its recommended rules
...react.configs.recommended.rules,
...react.configs["jsx-runtime"].rules,
},
});