-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
.settings.ignoreFiles doesn`t work #255
Comments
This is a bug. I now looking for this |
Hello Ritwickdey, (https://127.0.0.1:5500/index.html pls i need help with this. thanks |
@onimisiv Where exactly do you face the error, can you provide some screenshots? |
|
@onimisiv I think the problem with you is the extension cannot open your default browser, try open |
same problem come with me |
hey , its easy just set chrome as a default nav |
How to do that ? |
live server keeps showing me error message underneath my app after loading on Chrome browser. What should I do? |
tengo este mismo problema ayuda porfavo, pero mi puerto no es 5500, se esta cambiando pero no se por que |
Hello, I am using Live Server with the Firefox Live Server Web Extension plugin. The page refreshes when a file is saved, but this causes a continuous page refresh loop. The only way to stop it is to stop the "Live Server". The development is done in PHP with a tool that maintains a cache. Loading a page automatically updates files in tmp/cache/... I use the Watchman tool to monitor the actual modified files:
I can't find a "Live Server" output console in the list of Outputs in VSCode. Is there a way to view the names of the modified files that trigger a server reload? Is there a way to check that the added exclusion filters are being considered? Outputs of this type would be very useful:
Is it possible to add this feature to facilitate debugging? Thank you in advance. |
File updated : tmp/cache/sql_desc_a8601ad5.txt |
1 similar comment
File updated : tmp/cache/sql_desc_a8601ad5.txt |
Não aparece a opção da live, não está funcionando. |
Posting again problem that occured in #188
Could you check it out?
The text was updated successfully, but these errors were encountered: