Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@o2s/integrations.contentful-cms@1.0.2

Patch Changes

• db5d212: fix(integrations): emit live-preview components as .js so npm consumers can resolve them

  The shared API tsconfig inherited "jsx": "preserve" from the base config, so
  every .tsx file in these packages compiled to a .jsx file — even the ones
  that contain no JSX syntax at all, since the extension alone is enough. Their
  live-preview barrels then shipped require('./BlockEditAffordance') next to a
  BlockEditAffordance.jsx, and Node's CJS resolution inside node_modules only
  tries .js, .json and .node. Any project installing these packages from npm
  fails to build with Module not found: Can't resolve './BlockEditAffordance'.

  This never showed up here because our own apps import the workspace source
  rather than dist; it only breaks external consumers, which is why it survived
  a release.

  The API tsconfig now sets "jsx": "react-jsx", so these files emit .js. No
  behaviour changes: none of the affected components use JSX syntax — the one
  that renders markup already calls React.createElement directly — so nothing
  new is pulled in at runtime, and React is already a peer dependency of all
  three packages.

@o2s/integrations.mocked@2.1.1

Patch Changes

• db5d212: fix(integrations): emit live-preview components as .js so npm consumers can resolve them

  The shared API tsconfig inherited "jsx": "preserve" from the base config, so
  every .tsx file in these packages compiled to a .jsx file — even the ones
  that contain no JSX syntax at all, since the extension alone is enough. Their
  live-preview barrels then shipped require('./BlockEditAffordance') next to a
  BlockEditAffordance.jsx, and Node's CJS resolution inside node_modules only
  tries .js, .json and .node. Any project installing these packages from npm
  fails to build with Module not found: Can't resolve './BlockEditAffordance'.

  This never showed up here because our own apps import the workspace source
  rather than dist; it only breaks external consumers, which is why it survived
  a release.

  The API tsconfig now sets "jsx": "react-jsx", so these files emit .js. No
  behaviour changes: none of the affected components use JSX syntax — the one
  that renders markup already calls React.createElement directly — so nothing
  new is pulled in at runtime, and React is already a peer dependency of all
  three packages.

@o2s/integrations.strapi-cms@3.1.1

Patch Changes

• db5d212: fix(integrations): emit live-preview components as .js so npm consumers can resolve them

  The shared API tsconfig inherited "jsx": "preserve" from the base config, so
  every .tsx file in these packages compiled to a .jsx file — even the ones
  that contain no JSX syntax at all, since the extension alone is enough. Their
  live-preview barrels then shipped require('./BlockEditAffordance') next to a
  BlockEditAffordance.jsx, and Node's CJS resolution inside node_modules only
  tries .js, .json and .node. Any project installing these packages from npm
  fails to build with Module not found: Can't resolve './BlockEditAffordance'.

  This never showed up here because our own apps import the workspace source
  rather than dist; it only breaks external consumers, which is why it survived
  a release.

  The API tsconfig now sets "jsx": "react-jsx", so these files emit .js. No
  behaviour changes: none of the affected components use JSX syntax — the one
  that renders markup already calls React.createElement directly — so nothing
  new is pulled in at runtime, and React is already a peer dependency of all
  three packages.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: dfb00d87-0704-4d74-b42f-2d2a3cf172f3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Coverage Report for packages/configs/vitest-config

Status	Category	Percentage	Covered / Total
🔵	Lines	82.03%	2283 / 2783
🔵	Statements	81.16%	2399 / 2956
🔵	Functions	75.83%	640 / 844
🔵	Branches	68.29%	1570 / 2299

File Coverage

No changed files found.

Generated in workflow #960 for commit 6d243c2 by the Vitest Coverage Report Action