/*@__INLINE__*/ should be used in expressions, not on declaration, i.e.

export function foo() {
	console.warn("foo");
}

/*@__INLINE__*/
foo();
/*@__INLINE__*/
foo();
/*@__INLINE__*/
foo();
/*@__INLINE__*/
foo();

If you want to improve this, open an issue in terser, as this is outside of webpack, other minimizers use the same logic.

Feel free to feedback

Thanks for your answer.

/@INLINE/ should be used in expressions, not on declaration, i.e.

Ouch, I'm really blind. Didn't even noticed it after reading Terser documentation several times. I'm sorry for that, shame on me.

I assume I could use the DefinePluging to define CALL_FOO_INLINE( as being /* ... */ foo(. Enabling me to globally enable/disable the inlining when I think this is necessary.

I will come back later about bundles with performances constraints (other things to work on before).

@denis-migdal You can do it using DefinePluging, we inject a raw code, that is why we ask to use JSON.stringify for real JS values