add support for responsive styles in gen1 react sdk and memoize processBlock

[steve8708]

we don't use the post-processed responsiveStyles object that bindings influence, but instead the preprocessed one

gen2 supports this, but not gen1

also, i removed several repeat calls to processBlock() which is very bad for perf as that runs al l theb indings, and it was running many times per block instead of 1x like gen1 SDK

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: d28da60a8f8045e795dd6771b0af11bd53234e07

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit d28da60a8f8045e795dd6771b0af11bd53234e07. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx test @e2e/solid-start
nx test @snippet/qwik-city
nx test @snippet/sveltekit
nx test @snippet/svelte
nx test @e2e/vue
nx test @e2e/sveltekit
nx test @snippet/solid
nx test @e2e/angular-ssr

✅ Successfully ran 12 targets

• nx test @snippet/vue
• nx test @snippet/react-native
• nx test @e2e/react-native
• nx test @e2e/react-sdk-next-app
• nx test @e2e/react
• nx test @snippet/react
• nx test @snippet/react-sdk-next-pages
• nx test @snippet/react-sdk-next-app
• nx test @snippet/nuxt
• nx test @builder.io/sdks
• nx test @snippet/angular
• nx test @snippet/nextjs-sdk-next-app

---

Sent with 💌 from NxCloud.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
2708648	Triggered	Generic High Entropy Secret	0123b30f118c81702986f08baab222e4d812d168	packages/sdks-tests/src/specs/text-eval.ts	View secret
2708648	Triggered	Generic High Entropy Secret	0123b30f118c81702986f08baab222e4d812d168	packages/sdks-tests/src/specs/text-eval.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[samijaber]

Closing this due to being superseded by #3519 and #3522