Skip to content

chore(deps): update dependency @sanity/pkg-utils to v10.9.2#20

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sanity-pkg-utils-10.x-lockfile
Open

chore(deps): update dependency @sanity/pkg-utils to v10.9.2#20
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sanity-pkg-utils-10.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Dec 4, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@sanity/pkg-utils (source) 10.1.010.9.2 age confidence

Release Notes

sanity-io/pkg-utils (@​sanity/pkg-utils)

v10.9.2

Compare Source

Patch Changes

v10.9.1

Compare Source

Patch Changes

v10.9.0

Compare Source

Minor Changes
  • #​2955 935f6f6 Thanks @​stipsan! - Enable transpileTemplateLiterals by default in the babel.styledComponents transform, so unused styled components can be tree-shaken.

    The pure: true default has been emitting /*#__PURE__*/ annotations in front of tagged template expressions, a position no bundler supports (see rollup#4035), so the annotations were dropped and unused styled components were never tree-shaken - not by pkg-utils itself, and not by the bundlers of apps consuming the published package. Transpiling styled.button`...` to styled.button(["..."]) turns the styled component initializer into a plain call expression, which pure annotations are defined for:

    const UsedButton = /*#__PURE__*/ styled.button.withConfig({
      displayName: 'UsedButton',
      componentId: 'sc-1fal5wv-1',
    })(['cursor:pointer;'])

    With this shape, unused styled components are now removed from the build output, and the annotation survives into the published output so app bundlers (rollup, webpack, esbuild, etc) can drop exported styled components that the app never imports.

    To restore the previous output, set babel: {styledComponents: {transpileTemplateLiterals: false}} in package.config.ts.

Patch Changes

v10.8.2

Compare Source

Patch Changes
  • #​2934 d6cfe32 Thanks @​stipsan! - fix: preserve side-effect-only imports of external packages

    Tree-shaking no longer sets the equivalent of moduleSideEffects: 'no-external' and instead relies on the bundler's default (moduleSideEffects: true). Previously, binding-less side-effect imports of external package subpaths — e.g. import 'react-time-ago/locale/en' — were stripped from the output, breaking consumers that depended on those side effects. package.json sideEffects fields are still honored for bundled modules, so dead-code elimination is unaffected.

v10.8.1

Compare Source

Patch Changes

v10.8.0

Compare Source

Minor Changes
  • #​2888 59fdc02 Thanks @​stipsan! - feat: add strict dependency placement checks for well-known packages

    When running with --strict, package.json is now validated to ensure these packages are declared in the correct dependency fields:

    • react-is and @sanity/ui should not be in peerDependencies (use dependencies or devDependencies).
    • sanity, styled-components, react, and react-dom should not be in dependencies (use devDependencies and/or peerDependencies).
    • @types/react, @types/react-dom, and @types/node should not be in dependencies (use devDependencies and/or peerDependencies), and when listed in peerDependencies the version range should be *.
    • rxjs and @sanity/client should not be in peerDependencies (use dependencies or devDependencies).

    Each check is enabled by default at the error level and can be downgraded to warn or disabled via strictOptions in package.config.ts, e.g.:

    import {defineConfig} from '@​sanity/pkg-utils'
    
    export default defineConfig({
      strictOptions: {
        noReactDependency: 'warn',
        noSanityClientPeerDependency: 'off',
      },
    })
Patch Changes
  • #​2903 296482a Thanks @​stipsan! - feat: disallow @sanity/icons in peerDependencies

    When running with --strict, package.json is now validated to ensure @sanity/icons is not declared in peerDependencies (use dependencies or devDependencies instead). The check defaults to error and can be configured via noSanityIconsPeerDependency in strictOptions.

v10.7.2

Compare Source

Patch Changes
  • #​2897 de87bc9 Thanks @​stipsan! - fix: mirror the auto-added bundle.css export into publishConfig.exports

    In vanilla-extract compat mode, pkg-utils auto-writes the conditional "./bundle.css" export to package.json. It only updated the top-level exports, so packages that also declare publishConfig.exports ended up out of sync, and the next strict --check failed with publishConfig.exports: missing export path "./bundle.css" that exists in exports.

    The conditional CSS export is now mirrored into publishConfig.exports as well (when that field exists), keeping the two in sync. The entry is identical in both places since the CSS export has no source/development/monorepo conditions to strip. publishConfig.exports is never created when it is absent.

  • #​2899 97cbc33 Thanks @​stipsan! - Emit a <css>.d.ts declaration alongside the vanilla-extract compat-mode CSS shim, so dts export checkers that resolve a .d.ts for every export target don't crash on a missing declaration file.

v10.7.1

Compare Source

Patch Changes
  • #​2895 ba964f1 Thanks @​stipsan! - Revert the upgrade of @babel/core and @babel/preset-typescript to v8, pinning them back to v7

v10.7.0

Compare Source

Minor Changes
  • #​2890 c219497 Thanks @​stipsan! - feat: auto-wire the conditional bundle.css export for vanilla-extract

    When rollup.vanillaExtract is enabled, pkg-utils now (by default) bakes in the conditional CSS export pattern so userland no longer needs a manual rollup.output.intro + shim plugin + package.json export. This new "compat mode" (rollup.vanillaExtract.extract.compatMode, defaults to true):

    • injects the self-referential import "<pkg-name>/<name>" into each entry chunk,
    • emits a no-op <name>.js shim for runtimes that cannot import .css files, and
    • writes the conditional "./<name>" export to package.json (browser/style → the real CSS, node/default → the shim).

    The emitted CSS file name is configurable via rollup.vanillaExtract.extract.name (default "bundle.css"), and the vanillaExtract option is now fully typed (PkgVanillaExtractOptions) with its real defaults documented. Set extract.compatMode: false to opt out and wire these up yourself.

Patch Changes

v10.6.0

Compare Source

Minor Changes
  • #​2887 a6adaa1 Thanks @​stipsan! - feat: support conditional exports for CSS files

    CSS subpath exports may now be declared as a conditional object (a flat map of condition name to path) instead of only a plain string. This enables re-adding a import "<pkg>/bundle.css" statement that resolves to the real CSS file in bundler/browser environments, while resolving to a no-op JS shim in runtimes (like Node) that cannot import .css files directly:

    {
      "exports": {
        "./bundle.css": {
          "browser": "./dist/bundle.css",
          "style": "./dist/bundle.css",
          "node": "./dist/bundle.css.js",
          "default": "./dist/bundle.css.js"
        }
      }
    }
Patch Changes

v10.5.8

Compare Source

Patch Changes

v10.5.7

Compare Source

Patch Changes

v10.5.6

Compare Source

Patch Changes

v10.5.5

Compare Source

Patch Changes

v10.5.4

Compare Source

Patch Changes
  • #​2837 cc5b92a Thanks @​renovate! - fix(deps): Update dependency @​microsoft/api-extractor to ^7.58.8

  • #​2844 c27e975 Thanks @​jasonevines! - fix: preserve subpath imports of external packages in rolldown dts output

    Bare specifiers are now matched against their package name when deciding externals in the rolldown dts pipeline, so subpath imports of external dependencies (e.g. @sanity/client/stega) keep their original specifier instead of resolving to an absolute filesystem path in the emitted declarations.

v10.5.3

Compare Source

Patch Changes

v10.5.2

Compare Source

Patch Changes

v10.5.1

Compare Source

Patch Changes

v10.5.0

Compare Source

Minor Changes
  • #​2781 a8f395f Thanks @​rexxars! - feat: schedule JS build tasks for node export sub-conditions

    Exports with a node sub-condition (exports['.'].node.import / .require) now generate JS build tasks under runtime: 'node' using target.node, symmetric to how browser sub-conditions are already handled. Previously these outputs only got .d.ts files emitted while the JS was never built, leaving the declared output paths dangling. Isomorphic packages can now ship a node-specific entry without relaxing the package-wide browserslist.

Patch Changes

v10.4.18

Compare Source

Patch Changes

v10.4.17

Compare Source

Patch Changes

v10.4.16

Compare Source

Patch Changes

v10.4.15

Compare Source

Patch Changes

v10.4.14

Compare Source

Patch Changes

v10.4.13

Compare Source

Patch Changes

v10.4.12

Compare Source

Patch Changes

v10.4.11

Compare Source

Patch Changes

v10.4.10

Compare Source

Patch Changes

v10.4.9

Compare Source

Patch Changes

v10.4.8

Compare Source

Patch Changes

v10.4.7

Compare Source

Patch Changes

v10.4.6

Compare Source

Patch Changes

v10.4.5

Compare Source

Patch Changes

v10.4.4

Compare Source

Patch Changes

v10.4.3

Compare Source

Patch Changes

v10.4.2

Compare Source

Patch Changes

v10.4.1

Compare Source

Patch Changes

v10.4.0

Compare Source

Minor Changes
  • #​2538 a7bd216 Thanks @​copilot-swe-agent! - Auto-enable styled-components compiler when detected as peer dependency. If styled-components is in peerDependencies and babel-plugin-styled-components is in devDependencies, the babel plugin is automatically enabled without requiring explicit configuration. Users can disable this behavior by setting babel: { styledComponents: false } in package.config.ts.
Patch Changes

v10.3.5

Compare Source

Patch Changes

v10.3.4

Compare Source

Patch Changes

v10.3.3

Compare Source

Patch Changes

v10.3.2

Compare Source

Patch Changes

v10.3.1

Compare Source

Patch Changes

v10.3.0

Compare Source

Minor Changes
Patch Changes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 71a69e6 to e5dab92 Compare December 8, 2025 10:57
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.1.1 chore(deps): update dependency @sanity/pkg-utils to v10.1.2 Dec 8, 2025
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.1.2 chore(deps): update dependency @sanity/pkg-utils to v10.1.3 Dec 12, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from 09a4883 to 5a6ff40 Compare December 15, 2025 15:02
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.1.3 chore(deps): update dependency @sanity/pkg-utils to v10.2.0 Dec 15, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 5a6ff40 to 5a1bc16 Compare December 15, 2025 19:00
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.0 chore(deps): update dependency @sanity/pkg-utils to v10.2.1 Dec 15, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 5a1bc16 to eedb401 Compare December 18, 2025 23:25
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.1 chore(deps): update dependency @sanity/pkg-utils to v10.2.2 Dec 18, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from eedb401 to d1ab827 Compare December 19, 2025 16:13
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.2 chore(deps): update dependency @sanity/pkg-utils to v10.2.3 Dec 19, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from d1ab827 to 1df53f3 Compare December 30, 2025 10:53
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.3 chore(deps): update dependency @sanity/pkg-utils to v10.2.4 Dec 30, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 1df53f3 to 6bca28f Compare December 31, 2025 18:07
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.4 chore(deps): update dependency @sanity/pkg-utils to v10.2.5 Dec 31, 2025
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 6bca28f to e9ba232 Compare January 6, 2026 18:49
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.5 chore(deps): update dependency @sanity/pkg-utils to v10.2.6 Jan 6, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from e9ba232 to 5a021e5 Compare January 9, 2026 14:55
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.2.6 chore(deps): update dependency @sanity/pkg-utils to v10.3.0 Jan 9, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 5a021e5 to a3be58a Compare January 12, 2026 19:04
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.3.0 chore(deps): update dependency @sanity/pkg-utils to v10.3.2 Jan 12, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from 5177207 to a2fd39a Compare January 20, 2026 11:09
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.3.2 chore(deps): update dependency @sanity/pkg-utils to v10.3.3 Jan 20, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from a2fd39a to c055adf Compare January 23, 2026 20:52
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.3.3 chore(deps): update dependency @sanity/pkg-utils to v10.3.4 Jan 28, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from fe32a0f to f537abb Compare January 28, 2026 19:35
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.3.4 chore(deps): update dependency @sanity/pkg-utils to v10.3.5 Jan 28, 2026
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.4 chore(deps): update dependency @sanity/pkg-utils to v10.4.5 Mar 1, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 77e02da to 44b9a45 Compare March 3, 2026 15:01
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.5 chore(deps): update dependency @sanity/pkg-utils to v10.4.6 Mar 3, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 44b9a45 to f4ff654 Compare March 8, 2026 12:00
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.6 chore(deps): update dependency @sanity/pkg-utils to v10.4.7 Mar 8, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from f4ff654 to 485ff03 Compare March 9, 2026 06:50
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.7 chore(deps): update dependency @sanity/pkg-utils to v10.4.8 Mar 9, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 485ff03 to 8363e52 Compare March 13, 2026 13:13
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.8 chore(deps): update dependency @sanity/pkg-utils to v10.4.9 Mar 13, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 8363e52 to 69899fe Compare March 13, 2026 21:17
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.9 chore(deps): update dependency @sanity/pkg-utils to v10.4.10 Mar 16, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from 67954da to f6efd16 Compare March 18, 2026 14:49
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.10 chore(deps): update dependency @sanity/pkg-utils to v10.4.11 Mar 18, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from f6efd16 to 0ae198b Compare March 23, 2026 22:36
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.11 chore(deps): update dependency @sanity/pkg-utils to v10.4.12 Mar 23, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 0ae198b to 854e7a1 Compare March 24, 2026 19:01
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.12 chore(deps): update dependency @sanity/pkg-utils to v10.4.13 Mar 24, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from 2555e7d to d9babf6 Compare April 1, 2026 15:48
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch 2 times, most recently from 0d97cf4 to f1e51c8 Compare April 13, 2026 15:59
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.13 chore(deps): update dependency @sanity/pkg-utils to v10.4.14 Apr 13, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from f1e51c8 to ac67040 Compare April 15, 2026 19:18
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.14 chore(deps): update dependency @sanity/pkg-utils to v10.4.15 Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from ac67040 to 06138b2 Compare April 20, 2026 17:49
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.15 chore(deps): update dependency @sanity/pkg-utils to v10.4.16 Apr 20, 2026
@renovate renovate Bot force-pushed the renovate/sanity-pkg-utils-10.x-lockfile branch from 06138b2 to 50a89d2 Compare April 21, 2026 11:49
@renovate renovate Bot changed the title chore(deps): update dependency @sanity/pkg-utils to v10.4.16 chore(deps): update dependency @sanity/pkg-utils to v10.4.17 Apr 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants