Skip to content

fix(deps): update dependency @necto-react/components to v3 - #89

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/necto-react-components-3.x
Open

fix(deps): update dependency @necto-react/components to v3#89
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/necto-react-components-3.x

Conversation

@renovate

@renovate renovate Bot commented Apr 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@necto-react/components (source) 1.4.253.3.8 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

nectoutil/NodeKit (@​necto-react/components)

v3.3.8

Compare Source

Patch Changes

v3.3.7

Compare Source

Patch Changes

v3.3.6

Compare Source

Patch Changes

v3.3.5

Compare Source

Patch Changes

v3.3.4

Compare Source

Patch Changes

v3.3.3

Patch Changes
  • 04aba51: Migrate the build toolchain from tsdown to Vite+ (vp pack). The ESM build now emits .mjs (previously .js) and its types .d.mts; the CommonJS build (.cjs/.d.cts) is unchanged. Each package's exports, main, module, and types fields are updated to match, so normal package imports resolve exactly as before — only direct-to-dist/index.js deep imports are affected.

    This also migrates lint/format from Biome to oxlint/oxfmt (vp lint / vp fmt), the task runner from Turbo to pnpm, and bumps Vitest 3 → 4. Node 24+ is now required.

  • Updated dependencies [04aba51]

v3.3.2

Patch Changes

v3.3.1

Patch Changes
  • ac257f6: Fix Overflow flicker, "vanishing item" bug, and infinite-loop pitfall when
    parent re-renders without memoizing the items array.

    useOverflow now stores partition state as a single COUNT (number of
    visible items) instead of arrays of item references. visibleItems and
    hiddenItems are derived from the items prop + count at render time via
    useMemo. This decouples internal state from items prop identity:

    • Items reference churn (parent passing a freshly-built array on every
      render) no longer triggers any state update — partition state only
      changes when the layout demands it.
    • No flicker on parent re-renders.
    • Length changes still reset and re-measure, so adding/removing items
      works correctly.
    • The rendered visibleItems always reflect the latest items prop, never
      stale references from a previous reset.

    Symptom that motivated this: a tab list built on top of Overflow would
    visually jitter on every tab switch, and a tab near the visible/hidden
    boundary would appear to "vanish and come back" as the previous reset-
    based implementation re-ran the shrink loop on every parent re-render.

    Same architecture as react-overflow-list (BluePrint OverflowList) and
    similar proven libraries.

    Also adds a regression test for the no-flicker behavior and several new
    component-level tests covering empty items, omitted renderOverflow, and
    ref forwarding (function + object refs).

  • Updated dependencies [ac257f6]

v3.3.0

Minor Changes
  • ad6a4aa: Rename Overflow component renderer props for clarity.

    • renderItem (unchanged from original API)
    • renderMorerenderOverflow

    Earlier 3.2.x releases shipped these props but had broken type imports due to a
    build issue (hashed .d.ts filenames), so adoption is expected to be minimal.
    The rename clarifies that the prop renders the overflow indicator slot, not
    literally "more" content.

    Migration:

    // Before
    <Overflow
      items={tags}
      renderItem={(tag) => <Tag key={tag.id}>{tag.label}</Tag>}
      renderMore={({ count }) => <Chip>+{count}</Chip>}
    />
    
    // After
    <Overflow
      items={tags}
      renderItem={(tag) => <Tag key={tag.id}>{tag.label}</Tag>}
      renderOverflow={({ count, hidden }) => <Chip>+{count}</Chip>}
    />
Patch Changes
  • ad6a4aa: Fix TypeScript imports broken in previous releases due to hashed .d.ts filenames.

    Previous releases shipped dist/index-{hash}.d.ts and dist/index-{hash}.d.cts while
    package.json types and exports.types pointed at dist/index.d.ts — causing
    TS2306 / TS2307 errors in any consumer importing types. Root cause was a bug in
    rolldown-plugin-dts@0.13.x (transitive of tsdown@0.12.x) where entry chunks fell
    through to the hashed-filename template instead of the flat one.

    Resolved by bumping tsdown to ^0.21.10 (which pulls rolldown-plugin-dts@^0.23.x
    containing the fix from sxzz/rolldown-plugin-dts#132). Build now produces flat
    dist/index.d.ts and dist/index.d.cts, restoring type resolution for all consumers.

  • Updated dependencies [ad6a4aa]

v3.2.0

Minor Changes
  • 1633aec: Released to backfill changes
Patch Changes

v3.0.4

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Patch Changes
  • fbc449f: Add @emotion/jest to the test setup for necto-react-components. Extends vitest's expect with toHaveStyleRule so tests can assert emotion-generated CSS rules and pseudo-element styles. Also fixes ShadowBevel empty-string fallback for boxShadow and borderRadius props, and adds comprehensive static-style coverage for the component.

v3.0.0

Major Changes
  • 36723b4: Breaking: Remove Emotion css prop from ButtonProps and Primitive. The css prop and @emotion/react dependency have been removed entirely; styling now uses @emotion/styled exclusively.

    Breaking: Remove jsxImportSource: "@emotion/react" from tsconfig — the global css prop on JSX elements is no longer available.

    Internally, Box and ShadowBevel have been migrated from SCSS modules to @emotion/styled, allowing the entire SCSS/PostCSS build pipeline (sass, sass-embedded, postcss, postcss-modules, esbuild-sass-plugin) to be removed.

    New: capitalize added to @necto/strings — uppercases the first character of a string, empty-string safe.

Patch Changes

v2.0.0

Major Changes
  • 0284395: Breaking: Remove Emotion css prop from ButtonProps and Primitive. The css prop and @emotion/react dependency have been removed entirely; styling now uses @emotion/styled exclusively.

    Breaking: Remove jsxImportSource: "@emotion/react" from tsconfig — the global css prop on JSX elements is no longer available.

    Internally, Box and ShadowBevel have been migrated from SCSS modules to @emotion/styled, allowing the entire SCSS/PostCSS build pipeline to be removed. Primitive now uses createElement directly and lazily builds its tag-component map via a plain for...of loop.

    New: capitalize added to @necto/strings — uppercases the first character of a string, empty-string safe.

Patch Changes

Configuration

📅 Schedule: (in timezone America/New_York)

  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 automerge Kodiak label, DO NOT ADD! dependencies necto labels Apr 19, 2026
@renovate
renovate Bot force-pushed the renovate/necto-react-components-3.x branch 6 times, most recently from fb28d3e to fa11574 Compare April 22, 2026 20:40
@changeset-bot

changeset-bot Bot commented Apr 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: e50426e

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/necto-react-components-3.x branch 3 times, most recently from b83f617 to 1d33727 Compare April 27, 2026 00:59
@renovate
renovate Bot force-pushed the renovate/necto-react-components-3.x branch from 1d33727 to 62b74df Compare May 2, 2026 02:14
@renovate
renovate Bot force-pushed the renovate/necto-react-components-3.x branch 2 times, most recently from b4fc2ea to 8d61386 Compare July 9, 2026 17:05
@renovate
renovate Bot force-pushed the renovate/necto-react-components-3.x branch from 8d61386 to 4cef280 Compare August 29, 2026 01:13
@renovate

renovate Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 20 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 12, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/sprocket-ui/NodeKit/packages/@sprocketui-react/sprocketui-react-progress:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@necto-react%2Fhelpers: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/sprocket-ui/NodeKit/packages/@sprocketui-react/sprocketui-react-progress

@necto-react/helpers is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

@renovate
renovate Bot force-pushed the renovate/necto-react-components-3.x branch from 4cef280 to e50426e Compare August 29, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Kodiak label, DO NOT ADD! dependencies necto

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants