I'd like to kickstart a proper spec/docs for the #__PURE__ notation for easier reference as I see it always a bit unclear how it works.

So here I draft the basic version. Looking forward to your review and feedback!
https://github.com/js-compiler-hints-spec/compiler-hint-notations-spec-draft

GitHub - js-compiler-hints-spec/compiler-hint-notations-spec-draft: (Draft) Spec for __PURE__ etc compiler hint notations

(Draft) Spec for __PURE__ etc compiler hint notations - GitHub - js-compiler-hints-spec/compiler-hint-notations-spec-draft: (Draft) Spec for __PURE__ etc compiler hint notations

GitHub

Now in @rollupjs v3.24.0, `#__NO_SIDE_EFFECTS__` annotation is supported to mark function declarations as side-effects free. You might not need to add `#__PURE__` to every call anymore, while providing more optimized bundles!

Thanks a lot to @lukastaegert's great support and fast release!

https://github.com/rollup/rollup/pull/5024

feat: support `#__NO_SIDE_EFFECTS__` annotation for function declaration by antfu · Pull Request #5024 · rollup/rollup

This PR contains: bugfix feature refactor documentation other Are tests included? yes (bugfixes and features will not be merged without tests) no Breaking Changes? yes (breaking change...

GitHub

We pack 5 introduces a slew of new static analysis features, including /*#__pure__*/

https://webpack.js.org/blog/2020-10-10-webpack-5-release/

(Every sufficiently advanced dev tool contains an ad-hoc, informally specified compiler?)

Webpack 5 release (2020-10-10) | webpack

webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.