Library package cache "com.unity.burst@1.8.2"

I was on unity 2019 and now upgraded my project to 2021.

Now when I rebuild my library there is a big folder on library/package cache/com.unity.burst@1.8.2

however to my knowledge I don’t use burst in my project nor do I have it on the package manager. However the presence of this folder leads me to believe that burst comes by default in unity 2021. Do I lose anything by somehow unistalling burst from my project? Does it help during build times? Can I even remove it?

The folder is 600mb, not horrible but I could do without it if possible, since Im not using it anyway.

To my knowledge burst is something used for jobs/ecs? Which I dont use. Well, in the end I don’t really know what “com.unity.burst@1.8.2”.

Some advice would be appreciated, thanks!

Hi @karderos ,

If you open the Package Manager (Window > Package Manager) and select In Project, you should see Burst listed in there. If you click on it, the details pane will tell you which package has it as a dependency. It’s not installed by default when upgrading to 2021 from a previous version, AFAIK.

It’s possible that newer versions of some packages you use now depend on Burst to produce highly-optimized runtime code. Perhaps some of those packages were made compatible with jobs or changed to use them, even if you yourself do not directly use it.

8932032--1224540--Untitled.png
Here are the packages I have installed. Burst only shows when I switch to unity registry, it seems its installed as dependency of something. Maybe URP? Dont know enough about it

Oh, you may need to tick a checkbox named “Show Dependencies” in the Project Settings (Package Manager category). That will cause the package details (the right-hand view) to display a new section named “Dependencies” where you can see dependency information. (Disabling that “Show Dependencies” option is not very good because it just hides useful, relevant information behind a checkbox that’s far removed from the affected UI. I recommend leaving it on. It was removed in 2022.2, where it is now “always on”.)

thanks it seems that it was a dependency of urp