New Project "Bloatware".

[username132323232]

Every time when a new project is created, a number of packages are added automatically. Some are completely unnecessary. For example, why would one need “The JetBrains Rider Editor package”, “Visual Studio Code Editor” and “Visual Studio Editor” at the same time?

It takes some time to delete all the extra packages since after deleting each package there’s a recompile.

1. Is it possible to disable automatic install of a particular package?

2. If not, is there a fast way to delete all the unneeded packages with several recompiles?

Thanks.

[Kurt-Dekker]

Yuck. I hear your pain. I even have a standard blurb for it:

Extra unwanted packages in new projects (collab, testing, rider and other junk):

Temp/UnityEngine.TestRunner.dll Error

Recent versions of unity have an annoying habit of crapping useless packages into your project. When those packages inevitably have errors, this sort of thing happens. I have railed about it before. Go into the package manager and remove crap you don’t need, like the entire test runner and collab and whatnot. If you feel brave you can hand-edit the Packages/manifest.json file a lot faster than using the laggy package manager interface that only lets you remove one package at a time: [7287748-…

About the fastest way I have found to make a project and avoid all this noise is to create the project, then as soon as you see the files appear, FORCE-STOP (hard-kill) Unity (with the Activity Manager or Task Manager), then go hand-edit the Packages/manifest.json file as outlined in the above post, then reopen Unity.

Sometimes the package system gets borked from all this unnecessary churn and requires the package cache to be cleared:

Unity3D Package Cache errors(?)

[username132323232]

@Kurt-Dekker

Yuck. I hear your pain. I even have a standard blurb for it:

Extra unwanted packages in new projects (collab, testing, rider and other junk):

https://discussions.unity.com/t/846703/2

About the fastest way I have found to make a project and avoid all this noise is to create the project, then as soon as you see the files appear, FORCE-STOP (hard-kill) Unity (with the Activity Manager or Task Manager), then go hand-edit the Packages/manifest.json file as outlined in the above post, then reopen Unity.

Sometimes the package system gets borked from all this unnecessary churn and requires the package cache to be cleared:

https://stackoverflow.com/questions/53145919/unity3d-package-cache-errors/69779122

Thanks! This sounds a bit extreme, but I’ll try your idea on my next project

I wonder if manifest.json is generated from some template that we could edit to avoid this mess in the first place.