-
Notifications
You must be signed in to change notification settings - Fork 784
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
bug: Dev server not rebuilding when files change #4011
Comments
Hi @Slevinski, thanks for filing this issue and sorry that you've been having trouble with watch mode. I just tried out a quick One thing to note is that we only officially support up to node v16 at present. I don't think that would be likely to fix the problem, but there's some chance. If you're able to reproduce this reliably on your computer, is there any chance you'd be able to run a After cloning the Stencil repository you would do something like this: git bisect start # get started
git checkout v2.22.2
git bisect bad
git checkout v2.20.0
git bisect good then to test each commit you would do: npm run clean
npm ci
npm run build
npm pack then you could install the resulting npm i ../path/to/stencil-version.tgz Then you'd report on that commit to Git by doing (back in the Stencil repo): git bisect bad # if the issue still happens or git bisect good # if the issue isn't happening on that commit If that's too much no worries! I can try to figure out a windows VM to see if I can reproduce the issue. |
Thanks for the triage and the instructions. I can try this weekend. |
Perharps you can start your dev-server with the --verbose flag to see more: stencil build --dev --watch --serve --verbose I also have a problem with the watch mode in my project, i didn't have the time to check this against stencil-component-starter... but seems to be related. No Problem with 2.20.0, but since 2.21.0 i have these errors, just want to add additional info about what could be a problem.
|
After downgrading node to v16, I was able to build stencil/core. Unfortunately, when I built from source, the v2.20.0 dev server had the rebuild problem as well. I would update the code and the dev server wouldn't rebuild automatically.
I installed v2.20.0 from npm and the dev server worked properly by rebuilding when the code changed. I'll take another look later just to make sure I'm not missing anything... |
Hey folks 👋 I have two dev builds of Stencil that may fix this issue, one for Stencil v2 users, and one for Stencil v3 users. If anyone running into this particular issue could install either version (if you're on Stencil v2.X, use the first one. if you're on Stencil v3.X, use the second one) and report back as to whether that fixes the issue at hand, that be much appreciated.
Thanks! |
Excellent! The v3 works on my windows 11 with the Linux subsystem. The dev server rebuilds as expected. Thanks. |
Also now working with our projects, very nice ✅ |
The PR associated with this issue has landed and is included in today's v2.22.3 release and v3.2.0 release. As a result, I'm going to close this issue. Should this issue reappear, please feel free to open a new issue. Thanks again! |
Prerequisites
Stencil Version
2.20.2 and 3.0.0
Current Behavior
The stencil development server isn't rebuilding after files in src/ are changed.
stencil build --dev --watch --serve
This was working in version 2.20.0. I started the development server using the above command. I updated file src/component/fsw-sequence/fsw-sequence.tsx and the server would rebuild. After upgrading to v3.0.0 today, the development server stopped rebuilding. I downgraded to v2.20.2 and it still wouldn't rebuild. Downgrading to v2.20.0 fixed the issue and the development server rebuilds as expected.
Expected Behavior
The development server should rebuild the project when files are changed in src/.
System Info
Steps to Reproduce
Downgrade stencil/core to v2.20.2 and the problem still exists.
Downgrade stencil/core to v2.20.0 and the problem does not exist.
Code Reproduction URL
https://github.com/ionic-team/stencil-component-starter
Additional Information
No response
The text was updated successfully, but these errors were encountered: