Converting Breeze Next into Typescript, PNPM and Latest. #53938
Answered
by
mandatoryGithubUser
mandatoryGithubUser
asked this question in
General
Replies: 1 comment
-
The answer is the initial post |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
mandatoryGithubUser
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Breeze Next has no discussion board, so listing steps here so anyone converting can follow the steps easier.
Also to switch to PNPM and update everything to latest as auto-dependency updates aren't enabled. Though the
pnpm
switch is optional, just insert your package manger, or leave with npm and don't delete the package-lock.json.Updating everything and switching to pnpm
Installing Typescript
jsx
file to.tsx
, eglayout.jsx
->layout.tsx
pnpm dev
jsconfig.json
totsconfig.json
Making sure Typescript doesn't emit Eslint errors
pnpm remove @babel/eslint-parser @babel/preset-react
pnpm add -D @typescript-eslint/parser @typescript-eslint/eslint-plugin
Update eslint config to work with typescript eslint
Fix lint issues, final check and optional conversion of existing files
pnpm lint:fix
pnpm build
Renaming existing
.jsx
files can be done or just left as is. I find it easier to just leave them except for the main app router files, page, layout, errors, not-found.Beta Was this translation helpful? Give feedback.
All reactions