Visual Studio Code rebuilds for no good reason - visual-studio-code

Background:
When the project is already running (npm run start), and I make changes, and save. Then VS Code rebuilds and runs the project. Great!
But it is very frustrating when VS Code is running, and you look through the code (without changing or saving anything), then often VS Code rebuilds for no reason.
When this happens, one loses the DevTools browser inspector, and has to start all over again.
Questions:
So, is there a way to prevent VS Code from automatically rebuilding without having changed or saved anything?
And is it possible to keep the auto-rebuild-on-save functionality at the same time?

Related

Am I able to apply code changes while debugging using VS Code?

When using Visual Studio I am able to apply code changes and continue debugging. As far as I can tell this feature doesn't exist in VS Code, which means a lot of restarts and wasted time.
Is there a way to be able to add and execute new lines of code without restarting in VS Code?

VS Code freezes on tab change

I'm not really a coder but I use VS Code at work for various reasons on my mac.
If I move between VS Code and my browser, every time I open VS code it freezes for a moment. It freezes if I change tab or move file. Looking at my commit changes or doing anything with the in-built terminal doesn't cause it to freeze.
All the dependency packages are up to date. I've disabled all of the plugins and it still happens. VS Code is at the latest version, 1.67.0.
I really don't know what is causing it and would appreciate any help!

Dart/Flutter Debug Console Issue on Visual Studio Code

I'm trying to print('hi') inside Visual Studio Code's Debug Console using Dart/Flutter.
Whenever I perform a restart, it works just fine. As you can see in the debug console it prints: I/flutter: hi
Performing a restart takes up to one minute of loading time. This isn't very ideal.
Ideally I would prefer that print() displays on the console whenever I perform a hot reload (as this only a takes a few seconds).
Any help would be greatly appreciated!
You are running a flutter app. That's quite expensive even if your "app" is only a print. Depending on your machine, reloading or even restarting can take a while.
EDIT since the whole debugging setup required for flutter apps is run too.
If you want to run dart code only, consider creating a dart project without flutter.

Automatic Hot Restart and Reload Stopped Occurring - Flutter/VS Code

I've been learning Dart/Flutter on VS Code and the Hot Restart/Reload was always automatic (if I changed a color in the code, it automatically showed up on screen). I have to manually trigger the action now. I have no idea what changed.
I'm using VS Code and iOS emulator. I can't run SDK on Android Studio right because I'm on the new mac M1 processor.
Solutions I've tried:
Opened other Flutter projects and verified the hot restart isn’t
working on any of them (its not an import error like other posts have suggested)
I ensured that I can manually hot restart from VSCode and terminal to see changes
Flutter Doctor shows no errors
I ran Flutter Upgrade from the terminal anyway
I uninstalled and reinstalled Dart and Flutter from VS Code
I ensured VS Code’s autosave feature was on
I ensured VS Code’s “Dart: Flutter Hot Reload on Save” (and Restart) were both checked
I tried running with and without debugging
I restarted my computer and VS Code
Edit: I just installed Android Studio and cannot get an automatic hot reload here either. I connected it to iOS emulator, turned on automatic saving after 2 seconds of being idle, and still have to manually reload. Alternatively, I can go to the menu and click "Save All" and it will reload to update the UI (without me having to click a hot reload or restart icon). But, it's still manual.
Edit: 2/25/21: A "fix" has been introduced in the v3.20.0 beta.
https://dartcode.org/releases/v3-20/
Ok, I was finally pointed in the right direction for an answer.
Apparently, the automatic hot reload after an IDE autosave was a bug that some users found to be a useful feature. The intended functionality was to only trigger a hot reload on a manual activation. Thus, the bug (feature) was "fixed" taking this functionality away.
Feedback shown a light on the fact that some people found the bug useful and there is now an indication that this functionality will be returned in the future.
https://github.com/Dart-Code/Dart-Code/issues/3110
Edit: 2/25/21: A "fix" has been introduced in the v3.20.0 beta.
https://dartcode.org/releases/v3-20/
VSCode can be buggy sometimes and this problem is arguably the most annoying. I had this happen to me last week when I decided to use a barrel file with flutter web.
Meaning, I had a folder with all the components exported and then would import only that one file, like this
And then wherever I wanted all those files to be, I would add
import barrell.dart
Now this worked perfectly fine when I was working with flutter on mobile, and the second I went to flutter web my app would not hot reload.
I share this with you to say that I found out about this by a process of elimination. Took me a little bit, but I created a new project from the bottom up, added in each part one by one, and then I found that it was this barrell file that was messing the hot-reload up..
So my best advice is to do the same - start fresh with a new project, add back the pieces one-by-one and if you do find out what is causing the hang-up, I implore you to share it here:
https://github.com/flutter/flutter/issues

hot swapped warning without making any changes (Spring tool suite 3.9)

When running my code in debug mode, I keep getting 2 error messages:
Could not delete [path_to]\productiondb.log. May be locked by another process
I don't know what process might be locking it. It comes when I make changes to the code while my Pivotal tc Server is running in debug mode, but it dosent seem to create a lot's of trouble. Sometimes however, I get this warning:
Also due to some changes. I usally just restart the server and move on. This isen't the real problem, the real problem is that I get these messages when I havent doen any changes. Somethimes it accures when I run a certen part of the code, other times i occurs when I open certen codes in sts, however, it doen't seem to stop at the same place twice.
I am suspecting that this has something to do with git. I am using git to change between versions and doing tests. So I am thinking that STS has some of the code in memory from before I changed branche with git, and isen't updating it before I run or open the file with that code. But I am rather new to both sts and git, and can't be certan that it would work that way. If it is, does anyone know how to update sts after I have changed branch? If it is not, does anyone know what might causing it?
If you run an app in debug mode, the Eclipse Debugger tells the application when code gets changed and tries to use the debug API to swap in the new code into the running application. This is especially useful if you debug your code, hit a breakpoint, step through the code, fit the issue, change the code, and press save. At that moment, the Eclipse compiler updates the class file and tells the running JVM to swap in the new code. If that succeeds, the debugger will jump back to the last stack frame and the execution of your app will continue with the beginning of the method that you entered. This allows you to directly continue to debug and step through the updated code without restarting the app.
While this is a great feature of the JVM, it is very limited in terms of what scope of changes to the classes the JVM can deal with while doing this hot-swap. It is usually limited to method implementations. So adding new methods, adding or deleting members of the class, etc, are not supported. As a result, the above screenshot will appear. It means that the JVM wasn't able to hot-swap the changed code and will continue to run with the previously loaded code instead of the changed one.