while keeping it unchanged in the development environment.

What is the reason of this? For me, removing ?no-inline is feels expected as ?no-inline is just a special marker.

In the development environment, the purpose of not deleting it is so that users can see if it has been added with a ?no-inline marker, which I think would be better.

Doesn't that apply to the prod env as well? (I'm trying to understand the tradeoffs here)

My goal is to distinguish which ones I manually added the ?no-inline marker to in the dev env. When the asset file > assetsInlineLimit, it will be directly imported using the URL. And the asset file < assetsInlineLimit will be directly converted to base64, so I add a ?no-inline to it, it will also use the URL to import. Now if we remove the ?no-inline marker, these asset files > or < assetsInlineLimit can't see any difference in the URL(If we do not view the corresponding source code during development, but view the HTML in the browser, we will not know whether the ?no-inline marker is added or not.).

For prod env, I believe that building will not go wrong, ?no-inline is a development marker, it is not necessary to appear in the bundle, and ?no-inline will also take up a few network transmission bytes.