Include nested files in ESM compilation

[edbzn]

What I did

Fixed a compilation issue where nested ESM compiled files are overridden by CJS one due to a misconfiguration in the glob pattern when renaming files to .mjs.

Before, nested ESM files (like angular/dist/client/render.mjs) are not properly produced:

After, nested ESM files are correctly produced:

It is particularly an issue with @storybook/testing-angular where deep imports are used but proper ESM modules are not produced, leading to errors like:

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

1. Build any project like nx build angular
2. Check that dist/client/*.mjs files are produced

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Modified the glob pattern in TypeScript compilation script to properly handle nested ESM files, ensuring correct module format output for deep imports.

• Changed glob pattern from 'dist/*.js' to 'dist/**/*.js' in scripts/prepare/tsc.ts to include nested directory files
• Fixed issue where nested ESM files (e.g. angular/client/render.mjs) were being overridden by CommonJS versions
• Addresses compilation errors in @storybook/testing-angular where deep imports require proper ESM modules
• Ensures consistent module format output across nested directory structures

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

[greptile-apps]

_{1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Consider adding error handling around the file move operations in case of permission issues or disk space constraints

[greptile-apps]

LGTM

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}