[BUG] Development server usually doesn't update the extension or being extremely slow #664
Description
What happened?
Awesome framework guys 🥳! I enjoyed building stuff in it I will try to contribute on some parts. I experienced some problems though and I have to always manually stopping the dev server and running again to see the changes on my components. I'm aware by reading the docs in some situations it's necessary to do so but my changes has been related to the content ui files which should update as my understanding. I'm not sure how to debug this as well since it successfully builds every time but just doesn't reflect the changes on browser.
I am looking for any suggestions or input how to deal with this problem. I was thinking rm -rf .plasmo build when it gets slower but not sure if that's a good way of solving slowness.
My development setup might cause this issue, I will download chrome try on that as well. Currently using:
-
Brave
-
Webstorm
-
For the extension, these are my deps:
"dependencies": {
"@hookform/resolvers": "^3.1.1",
"@radix-ui/react-alert-dialog": "^1.0.4",
"@radix-ui/react-checkbox": "^1.0.4",
"@radix-ui/react-dialog": "^1.0.4",
"@radix-ui/react-dropdown-menu": "^2.0.5",
"@radix-ui/react-icons": "^1.3.0",
"@radix-ui/react-label": "^2.0.2",
"@radix-ui/react-select": "^1.2.2",
"@radix-ui/react-slot": "^1.0.2",
"@radix-ui/react-switch": "^1.0.3",
"@radix-ui/react-tabs": "^1.0.4",
"class-variance-authority": "^0.6.1",
"clsx": "^1.2.1",
"lucide-react": "^0.258.0",
"plasmo": "0.77.5",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-hook-form": "^7.45.1",
"tailwind-merge": "^1.13.2",
"tailwindcss": "3.3.2",
"tailwindcss-animate": "^1.0.6",
"zod": "^3.21.4"
},
"devDependencies": {
"@plasmohq/prettier-plugin-sort-imports": "3.6.4",
"@types/chrome": "0.0.239",
"@types/node": "20.3.2",
"@types/react": "18.2.14",
"@types/react-dom": "18.2.6",
"autoprefixer": "10.4.14",
"postcss": "8.4.24",
"prettier": "2.8.8",
"typescript": "5.1.6"
}Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
There is no output. Everything seems fine.(OPTIONAL) Contribution
- I would like to fix this BUG via a PR
Code of Conduct
- I agree to follow this project's Code of Conduct
- I checked the current issues for duplicate problems.