CodSpeed Performance Report

Merging#19929 willdegrade performances by 41.68%

_{Comparingpart-of-19902 (2dbf651) withmain (c647cf1)}

Summary

❌ 1 regression
✅ 41 untouched

⚠️Please fix the performance issues oracknowledge them on CodSpeed.

Benchmarks breakdown

hi! I think there is nothing wrong with the current result.

A deferred namespace object is an ECMAScript module namespace object, since it's impossible to export a symbol-named entry in an ES Module (not possible toexport const [Symbol.something] = ...), reflecting symbol names in the final namespace is not correct.

@Jack-Works I agree aboutECMAScript module namespace object, but in my example we importcommonjs module and usingmodule.exports, withoutdefer we provide compatibility (old way) like you have named export, withdefer we don't do it, it can be confusing by developers

@Jack-Works I agree aboutECMAScript module namespace object, but in my example we importcommonjs module and usingmodule.exports, withoutdefer we provide compatibility (old way) like you have named export, withdefer we don't do it, it can be confusing by developers

The difference of exported keys:

-Symbol(comet)-Symbol(meteor)+default

If we change the mode, that means any symbol (even non-exist one) access will also trigger the module evaluation. I'm not sure if that is what we want.

maybe cc@nicolo-ribaudo ?

Yeah, let/s wait@nicolo-ribaudo answer