Skip to content

chore(deps): update lynx #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update lynx #89

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2025

This PR contains the following updates:

Package Change Age Confidence
@lynx-js/qrcode-rsbuild-plugin (source) 0.3.6 -> 0.4.0 age confidence
@lynx-js/react (source) 0.109.0 -> 0.111.0 age confidence
@lynx-js/react-rsbuild-plugin (source) 0.10.1 -> 0.10.6 age confidence
@lynx-js/rspeedy (source) 0.9.7 -> 0.10.0 age confidence

Release Notes

lynx-family/lynx-stack (@​lynx-js/qrcode-rsbuild-plugin)

v0.4.0

Compare Source

Minor Changes
  • Support "Type to search" when switching entries and schema. (#​1115)
lynx-family/lynx-stack (@​lynx-js/react)

v0.111.0

Compare Source

Minor Changes
  • Allow some <list-item/>s to be deferred and rendered in the background thread. (#​204)

    Use the following syntax:

    <list>
    -  <list-item item-key="...">
    +  <list-item item-key="..." defer>
          <SomeHeavyComponent />
      </list-item>
    </list>

    You should render your heavyweight components with the defer attribute to avoid blocking the main thread.

Patch Changes
  • Add missing alias of @lynx-js/react and preact in testing library, it will fix the Failed to resolve import "@&#8203;lynx-js/react/internal" error in node_modules. (#​1182)

  • Allow any types of dataProcessors in lynx.registerDataProcessors. (#​1200)

  • Make loadLazyBundle being able to render the content on the first screen of the background thread. (#​1212)

  • Fixed: An issue where the lynxViewDidUpdate callback did not trigger when data was updated from native. (#​1171)

    Notice:

    • Even if no data changes are actually processed after calling updateData(), the lynxViewDidUpdate callback will still be triggered.
    • Only one lynxViewDidUpdate callback will be triggered per render cycle. Consequently, if multiple updateData() calls are made within a single cycle but the data updates are batched, the number of lynxViewDidUpdate callbacks triggered may be less than the number of updateData() calls.
  • Supports act in testing library. (#​1182)

    import { act } from '@&#8203;lynx-js/react/testing-library';
    
    act(() => {
      // ...
    });

v0.110.1

Compare Source

Patch Changes
  • Fix a memory leak when using <list/>. (#​1144)

v0.110.0

Compare Source

Minor Changes
  • Fixed closure variable capture issue in effect hooks to prevent stale values and ensured proper execution order between refs, effects, and event handlers. (#​770)

    Breaking Changes:

    • The execution timing of ref, useEffect() callback, componentDidMount, componentDidUpdate, componentWillUnmount and the callback of setState have been moved forward. These effects will now execute before hydration is complete, rather than waiting for the main thread update to complete.
    • For components inside <list />, ref callbacks will now be triggered during background thread rendering, regardless of component visibility. If your code depends on component visibility timing, use main-thread:ref instead of regular ref.
Patch Changes
  • Fixed two memory leaks: (#​1071)

    1. When JSX is rendered on the main thread and removed, FiberElement can still be referenced by __root.__jsx through props.children;

    2. When the SnapshotInstance tree is removed from the root node, its child nodes form a cycle reference because the __previousSibling and __nextSibling properties point to each other, thus causing a FiberElement leak.

  • Optimize the error message when snapshots cannot be found in the main thread. (#​1083)

  • Fix a problem causing MainThreadRefs to not be updated correctly during hydration when they are set to main-thread:refs. (#​1001)

  • Add snapshot id report when throwing snapshotPatchApply failed: ctx not found error. (#​1107)

  • Fix a bug in ReactLynx Testing Library that rendered snapshot of inline style was normalized incorrectly (eg. flex:1 was normalized to flex: 1 1 0%; incorrectly). (#​1040)

v0.109.2

Compare Source

Patch Changes
  • Support for locating errors in the source code directly on the device when exceptions occur when using MTS. (#​1019)

    This requires Lynx engine v3.4 or later.

  • Fix the "main-thread.js exception: ReferenceError: __webpack_require__ is not defined" error in HMR. (#​985)

    This error occurred when setting output.iife: true, which is the default value in @lynx-js/rspeedy v0.9.8.

v0.109.1

Compare Source

Patch Changes
  • Support the 'main-thread' directive as an alias for 'main thread'. (#​970)

  • Reduce calls to __AddInlineStyle by pass non-literal object directly to __SetInlineStyles. (#​941)

lynx-family/lynx-stack (@​lynx-js/react-rsbuild-plugin)

v0.10.6

Compare Source

Patch Changes

v0.10.5

Compare Source

Patch Changes

v0.10.4

Compare Source

Patch Changes

v0.10.3

Compare Source

Patch Changes

v0.10.2

Compare Source

Patch Changes
lynx-family/lynx-stack (@​lynx-js/rspeedy)

v0.10.0

Compare Source

Minor Changes
  • Bump Rsbuild v1.4.3 with Rspack v1.4.2. (#​1204)

    See Announcing Rspack 1.4 for more details.

  • Deprecated output.distPath.intermediate (#​1154)

    This option is never read and will be removed in the future version.

v0.9.11

Compare Source

Patch Changes
  • Enable fine-grained control for output.inlineScripts (#​883)

    type InlineChunkTestFunction = (params: {
      size: number
      name: string
    }) => boolean
    
    type InlineChunkTest = RegExp | InlineChunkTestFunction
    
    type InlineChunkConfig =
      | boolean
      | InlineChunkTest
      | { enable?: boolean | 'auto', test: InlineChunkTest }
    import { defineConfig } from '@&#8203;lynx-js/rspeedy'
    
    export default defineConfig({
      output: {
        inlineScripts: ({ name, size }) => {
          return name.includes('foo') && size < 1000
        },
      },
    })
  • docs: remove chunks: 'all' in comments (#​1168)

v0.9.10

Compare Source

v0.9.9

Compare Source

Patch Changes
  • Set optimization.emitOnErrors when DEBUG is enabled. (#​1000)

    This is useful for debugging PrimJS Syntax error.

v0.9.8

Compare Source

Patch Changes
  • Fix the "SyntaxError: invalid redefinition of parameter name" error. (#​949)

    Remove the default output.iife: false from Rspack.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the bot:renovate label Jul 1, 2025
Copy link

changeset-bot bot commented Jul 1, 2025

⚠️ No Changeset found

Latest commit: 3a6e4f6

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

@renovate renovate bot force-pushed the renovate/lynx branch from f287a94 to 3a6e4f6 Compare July 4, 2025 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants