Jessica Franco

@lelandrichardson no. 10 in there could maybe be ignored in `async` contexts, at least when optimizing for v8. It'll be either in code transpiled into a Promise-based driver (no try/catch),...

All of the "optimization killers" (except for hash table mode objects) should not be a problem anymore with v8 5.5 anyway.

This also happened to be a blocker for a smartphone-specific project at work. I'll link this to the person involved so he can check if this works 🤔

Note that it's important to know when a dynamically inserted style is loaded. Not knowing this leads to FOUC, which can be disastrous if you're doing things like `getBoundingClientRect` on...

I present to you this horribleness as a workaround, which does work on Chrome 14, one of the affected browsers according to https://pie.gd/test/script-link-events/:  I did not _actually_ test this...

~~The problem seems to be that `next/head` *discards* all `strategy='beforeInteractive'` scripts if they don't have a `src` defined:~~ https://github.com/vercel/next.js/blob/9ac231a0b4f4e9cbd8fffe1f9155962f5b212df4/packages/next/pages/_document.tsx#L319 ~~The `children` prop is being correctly forwarded (by being spread with...

@arackaf Also, the second one might invoke setters, and you have to be careful to correctly forward your arguments to super.

I see the declarative field as simpler from a mental model standpoint, as a declared field is just a field in your instance, and it avoids for you all the...

The new `indent` shipped :tada: Any thoughts on how the new indent setting will look like for `standard`? For example, one point I am wondering about is whether `MemberExpression` should...

Note also that you can't _just_ rename the rule from `no-` to "no `no-`". You also have to flip what `"always"` / `"never"` / et al mean. Not saying it...