Skip to content
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

Auto reload issue after upgrade to 2.0.2 #429

Closed
trhamann opened this issue Aug 3, 2021 · 6 comments
Closed

Auto reload issue after upgrade to 2.0.2 #429

trhamann opened this issue Aug 3, 2021 · 6 comments

Comments

@trhamann
Copy link

trhamann commented Aug 3, 2021

I have upgraded from version 1.6.0 to version 2.0.2. No errors are occurring however the auto reload process is happening more frequently than before. Opening / closing and searching for files in the text editor and modifying CSS files all trigger the auto reload. We do not have any custom "autoImport" config in the app.

Is this a bug or am I missing a configuration change in the upgrade from version 1 to version 2?

I am running:

  • ember-auto-import 2.0.2
  • ember-source 3.21.1
  • webpack 5
@ef4
Copy link
Collaborator

ef4 commented Aug 3, 2021

Interesting. Is your ember-cli printing which files it thinks changed?

@ef4
Copy link
Collaborator

ef4 commented Aug 3, 2021

And what editor are you using? Some of them create temp files that have been known to cause issues in the past.

@trhamann
Copy link
Author

trhamann commented Aug 3, 2021

We are using Visual Studio Code and it prints out the file that was opened. We are able to get it to happen using touch in a Linux terminal as well.

@ef4
Copy link
Collaborator

ef4 commented Aug 3, 2021

This doesn't sound like an ember-auto-import specific problem to me. The only time we do any file watching is if you use the watchDependencies option, otherwise that's all left up to ember-cli.

@trhamann
Copy link
Author

trhamann commented Aug 3, 2021

Ok, thank you for your time.

@trhamann trhamann closed this as completed Aug 3, 2021
@nag5000
Copy link

nag5000 commented Dec 16, 2021

The same bug: #469

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants