CLI: add warning when main config does not use default exports

[yannbf]

Telescoping off of #20797

What I did

This PR does a couple of things:

1. Introduces a new piece of metadata in ConfigFile from csf-tools, where whenever you use readConfig, you will be able to check whether a main.js file contains a default export or not by using mainConfig.hasDefaultExport
2. Adds a warning to support enforcing the "default exports" format in main.js. It happens in a core piece of code which gets executed in build-dev, build-static and telemetry. It warns users only once.
   Please refer to CLI: generate main config with default exports #20797 for more context.

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[IanVS]

I guess we should remove this suggestion from the vite builder readme, then.

storybook/code/lib/builder-vite/README.md

Line 137 in eb3cc8d

Or alternatively, you can use named exports:

[yannbf]

I guess we should remove this suggestion from the vite builder readme, then.

storybook/code/lib/builder-vite/README.md

Line 137 in eb3cc8d

Or alternatively, you can use named exports:

Thanks! It's addressed here #20801

[socket-security]

Socket Security Pull Request Report

👍 No new dependency issues detected in pull request

Pull request report summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script confusion	✅ 0 issues
Bin script shell injection	✅ 0 issues
Shell access	✅ 0 issues
Uses eval	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
GitHub dependency	✅ 0 issues
New author	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues
AI detected malware	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@2.4.2

Powered by socket.dev

[stevezhu]

@yannbf glob is a peer dep of glob-promise. Should probably be reinstalled.
https://github.com/ahmadnassri/node-glob-promise/blob/v6.0.2/package.json#L40-L42

 WARN  Issues with peer dependencies found
apps/projection
└─┬ @storybook/addon-essentials 7.0.0-beta.39
  └─┬ @storybook/addon-controls 7.0.0-beta.39
    └─┬ @storybook/blocks 7.0.0-beta.39
      └─┬ @storybook/docs-tools 7.0.0-beta.39
        └─┬ @storybook/core-common 7.0.0-beta.39
          └─┬ glob-promise 4.2.2
            └── ✕ missing peer glob@^7.1.6
Peer dependencies that should be installed:
  glob@^7.1.6

But also is it really necessary to install an entire wrapper package just to make glob return a promise? It's just a 5 line promise wrapper.

https://github.com/ahmadnassri/node-glob-promise/blob/master/lib/index.js

[ndelangen]

I'll fix this today, thank you for bringing this to our attention @stevezhu