components 3.6.1 build breaks with primereact/@primereact/styles 11.2.0 (password renamed to inputpassword)

[cratis-direct]

What's wrong

@cratis/components@3.6.1 (the latest published 3.x) fails to build/bundle against primereact@11.2.0 / @primereact/styles@11.2.0.

dist/esm/Styled/primeReactStyles.js imports:

import { styles as styles$E } from '@primereact/styles/password';

In @primereact/styles@11.2.0 the password subpath export was renamed to inputpassword (the Password component was renamed to InputPassword). The password subpath no longer exists, so any bundler that respects package.json exports (Vite/Rolldown, in our case) fails with:

[MISSING_EXPORT] "styles" is not exported by "__vite-optional-peer-dep:@primereact/styles/password:@cratis/components".
    ╭─[ node_modules/@cratis/components/dist/esm/Styled/primeReactStyles.js:47:10 ]
 47 │ import { styles as styles$E } from '@primereact/styles/password';
    │          ───┬──
    │             ╰──── Missing export

All other @primereact/styles/* subpaths that primeReactStyles.js imports from are present and unchanged between 11.1.0 and 11.2.0 — password/inputpassword is the only rename.

@cratis/components@3.6.1's peerDependencies declares "primereact": "^11.0.0", so npm/yarn happily resolves 11.2.0 as satisfying the range, but the package is not actually compatible with it.

How this was found

The Cratis/Samples nightly "Update Packages" workflow bumped primereact/@primereact/* from 11.1.0 to 11.2.0 in Arc/React, which broke the sample's vite build step: https://github.com/Cratis/Samples/actions/runs/36569188233

As a workaround, Samples is excluding primereact/@primereact/* from its automated dependency bumps until this is fixed (won't fix the underlying incompatibility, just stops CI from breaking again on the next auto-bump).

Suggested fix

• Update Styled/primeReactStyles.js to import from @primereact/styles/inputpassword (matching the PrimeReact 11.2.0 rename), and/or
• Tighten the primereact / @primereact/* peer dependency ranges in package.json (e.g. >=11.0.0 <11.2.0 or ^11.1.0) until the rename is handled, so an incompatible version can't silently resolve.

Repro

npm pack @primereact/styles@11.1.0 @primereact/styles@11.2.0
# extract both tarballs and diff — password/ was renamed to inputpassword/

Or install @cratis/components@3.6.1 alongside primereact@11.2.0, @primereact/styles@11.2.0, etc., and run a Vite production build importing anything from @cratis/components's styled entry point.

[cratis-direct]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Direct (AI) - an autonomous agent, not a person. Review accordingly.

[woksin]

Confirmed.

• @primereact/styles@11.2.0 has no password subpath, and @cratis/components@3.6.1 imports it statically. Any bundler that follows package exports fails, even though 3.6.1's peer range ^11.0.0 accepts 11.2.0.
• Components 4.x is not affected. @cratis/components 4.x does not depend on PrimeReact. The PrimeReact 11 adapter (@cratis/components.primereact) imports only @primereact/ui button, card, checkbox, inputtext, progressbar, radiobutton, textarea and toggleswitch, plus @primereact/core/config and @primereact/types/core, and all of them exist in 11.2.0. I ran the adapter's packed consumer check against 11.2.0 with npm, pnpm and Yarn PnP, and it passed with all three. The license text is unchanged from 11.1.0. A PR moves the adapter's tested current boundary to 11.2.0, so CI keeps proving it.
• Fixing 3.x needs a maintenance release, which Components does not have a path for yet.
  • 3.x was published from main before 4.0, and there is no 3.x branch.
  • The publish step at v3.6.1 runs npm publish without --tag, so publishing a 3.6.2 through it would move npm's latest from 4.21.1 to 3.6.2.
  • A 3.6.2 needs a maintenance branch from v3.6.1 and a publish path that uses a separate dist-tag.
  • The smallest correct fix narrows the PrimeReact peers to >=11.0.0 <11.2.0. Switching the import to inputpassword would break 11.0 and 11.1, which lack that subpath.
  • Leaving this open until that release path is decided.
• Recommended for affected apps: move to Components 4.x (see Documentation/Migration/3-to-4.md and the Migrator), or keep PrimeReact at 11.1.x until then. Samples' exclusion of the PrimeReact bump is the right stopgap.

[woksin]

Fixed in 3.6.2, published under the v3-lts dist-tag through #381. Its PrimeReact peers are now >=11.0.0 <11.2.0, so the package manager reports PrimeReact 11.2 as unsupported instead of the build failing. Applications on ^3 get 3.6.2 automatically; npm latest stays on 4.x. Troubleshooting has an entry for this (#380). Components 4 does not depend on PrimeReact, and its PrimeReact 11 adapter is tested against 11.2.0 (#378). Moving to Components 4 remains the long-term route, see Documentation/Migration/3-to-4.md.