-
Manage NodeJS environments with nvm
-
Use PNPM instead of npm
npm install -g pnpm
a. Then run
pnpm setup
and restart vs code or shell sessionb. Set up a pnpm-workspace.yaml file and a package.json with
pnpm init
-
Set up healthy typescript eslint and prettier configurations
a. Run
pnpm install --save-dev eslint-config-prettier
to remove built-in prettier configurationsb. Set up prettierrc and ignore files
c. Set up root eslintrc. Extend project eslintrc files from this.
-
Define a set of recommended vs code extensions for the workspace
https://code.visualstudio.com/docs/editor/extension-marketplace#_workspace-recommended-extensions
esbenp.prettier-vscode
dbaeumer.vscode-eslint
yoavbls.pretty-ts-errors
ms-vscode.vscode-typescript-next
ms-playwright.playwright
Firefox users: firefox-devtools.vscode-firefox-debug
eamodio.gitlens
dsznajder.es7-react-js-snippets
planbcoding.vscode-react-refactor
wix.vscode-import-cost
burkeholland.simple-react-snippets
-
Define a workspace tsconfig then extend it in each project
-
Use pnpm create vite to create react projects. Use pnpm init for libraries.
a. Ensure vite config is at the root of the repo and is piped into commands (
vite run --config ../../vite.config.js
) -
Install vitest ontop of jest configs for each project with tests
-
For React projects with tests, install testing-library/react
pnpm install --save-dev @testing-library/react
a. In addition, build a common wrapper at our root to render localization, theming, etc (test-utils.tsx)
-
Notifications
You must be signed in to change notification settings - Fork 1
bitobrian/react-tooling
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published