These assets are suppose to be committed.

@driesvints Could you share a reason?

These assets are equivalent to the version that's locked in composer.lock so they need to be committed. Changing this would also require us to change the install docs of nova, telescope, horizon, etc

From this point of view we can say that the assets in the build folder depend on the versions locked in package-lock.json so they need to be commited.
It looks contradictory that we don't commit the public/build folder now, but commit the public/vendor folder, but not commit /vendor folder.

As you have noticed these assets are equivalent to the version that's locked in composer.lock, in other words – just a copy from current vendor versions.
If we now required to launch npm install && npm run build to make client side ready to use it would be consistent to supplement this with the publication of the vendor assets.

If the question is on changing the docs, lets make a short conversation and I will do my best 🤝 🙂

Why wait four or five years (as it was with the main bundle) when we can bring such a simple and consistent change already #4118 #4625 #5646

We're not revising this, sorry.

These assets are equivalent to the version that's locked in composer.lock so they need to be committed. Changing this would also require us to change the install docs of nova, telescope, horizon, etc

That is, after installing the project through composer create-project you should always do git add .?
Is this considered the correct way?