-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hot Reload doesn't work when creating project with TypeScript support (Class based) #10527
Comments
What create settings are you using? I'm currently using TypeScript and hot reload works for me. |
@MatthewSH I've just created a new one but using Options API this time and it worked =) It failed when I selected class based component style. Css Processor: |
I just created a project to confirm this. This issue that I experienced was in Quasar v2, not v1. Have no tested on v1. Setup/Version InformationCreate OptionsCSS Preprocessor: None Quasar InfoNodeNodeJS: 14.17.4 GlobalNPM: 6.14.14 Packagesquasar: 2.0.4 I can confirm that with the class-based Vue/Quasar setup, the hot reload is not functioning correctly. It does detect changes and recompiles them, it does this every change I make. Upon further inspection with this, and I'll have to compare it to the functioning hot reload on another version but it is detecting the changes on the web end, just marking them as invalid? |
Thanks @MatthewSH at least we know this is a genuine issue now and not just my laptop going crazy ! cheers |
I can confirm that issue. Changes in the created Maybe related to this? |
Thanks, @dickerpulli! Guess I missed it when I glanced through their repo, or I did miss it. I wasn't really looking though, just like scanning very quickly. That's on me. However, it does look like the devs aren't acknowledging the issue so not sure how likely it is to be fixed. |
Closing this in favor of #9302 which is where we're posting our findings on the problem The The problem is related to Quasar interaction with Class API, eg. you won't get it into a Vue CLI project We tried reaching for the core team, but the repo seems unmaintained since months |
@ronniechew you wrote you're using Qv1, but we are aware these problems are only present on Qv2. |
@IlCallo I think that's the CLI version. Here's my Operating System - Windows_NT(10.0.18363) - win32/x64 Global packages Important local packages Quasar App Extensions |
We found the culprit, a PR is under its way to vue-loader repo: vuejs/vue-loader#1897 |
Seems that my PR has been merged and the vue-loader team has released a new version. Enjoy! |
Hi @dickerpulli, yes for me didn't work on Index.vue too, and that forced me to change the file name to be solved. |
Hot reload does not work when you create new project with
quasar create
with TypeScript support.Tried creating a new project without TypeScript and hot reload work out-of-the-box as expected.
To Reproduce
Steps to reproduce the behavior:
quasar create test-quasar-ts
quasar dev
Expected behavior
Hot reload should work and reflect changes on the fly
Platform (please complete the following information):
Quasar Version: 1.2.1
@quasar/app Version: 2.0.4
Quasar mode:
Tested on:
OS: Windows_NT(10.0.18363) - win32/x64
Node: 14.17.0
NPM: 7.7.6
Yarn: 1.21.1
Browsers: Chrome Version 92.0.4515.159 (Official Build) (64-bit)
iOS:
Android:
Electron:
Additional context
It works fine when I do
quasar create
but not selecting TypeScript support.The text was updated successfully, but these errors were encountered: