Solid 1.6 adds changes to JSX spreads on native elements, mergeProps, and splitProps to bypass creating Proxies when possible, which makes Solid viable for targeting environments that don't support Proxies. However, certain cases will still force creation of Proxies, and it's not obvious when this happens. Following this thread, I'm adding an opt-in rule that will catch these cases in first-party code to help people avoid accidentally using Proxies.
Solid 1.6 adds changes to JSX spreads on native elements,
mergeProps, andsplitPropsto bypass creating Proxies when possible, which makes Solid viable for targeting environments that don't support Proxies. However, certain cases will still force creation of Proxies, and it's not obvious when this happens. Following this thread, I'm adding an opt-in rule that will catch these cases in first-party code to help people avoid accidentally using Proxies.