`cosmos --expose-imports` seems to have stopped building imports at some point about react-cosmos

[oponder]

setting our package.json to next seems to fix the issue:

    "react-cosmos": "next",
    "react-cosmos-dom": "next",
    "react-cosmos-renderer": "next",

// yarn.lock

... 

[email protected]:
  version "6.0.0-beta.5"
  resolved "https://registry.yarnpkg.com/react-cosmos-core/-/react-cosmos-core-6.0.0-beta.5.tgz#66a1dbc2d234e2f55248be51b6dd06ed0be8a942"
  integrity sha512-6htNpF6YGQZIAWMRa+XZ9ltpIzIt0L2ZrrO+yXuTYH/OfQnvBb9awLvha/XT290KX/LVhKl+H95dMqBMuEENRA==
  dependencies:
    js-base64 "^3.7.5"
    lodash-es "^4.17.21"
    react-is "^18.2.0"

react-cosmos-dom@next:
  version "6.0.0-beta.6"
  resolved "https://registry.yarnpkg.com/react-cosmos-dom/-/react-cosmos-dom-6.0.0-beta.6.tgz#8c00ad94d8fb653739b98566dc8f0b8a61a27033"
  integrity sha512-3xZuIuJy3cjh+9m7E5TF4HUhJTj1KKtmHp4P0djfbvzZTvQsALLluQmn0OddU1RiSN98sJiPruWhcEZC2SmdRg==
  dependencies:
    lodash-es "^4.17.21"
    react-cosmos-core "6.0.0-beta.5"
    react-cosmos-renderer "6.0.0-beta.5"

[email protected], react-cosmos-renderer@next:
  version "6.0.0-beta.5"
  resolved "https://registry.yarnpkg.com/react-cosmos-renderer/-/react-cosmos-renderer-6.0.0-beta.5.tgz#d51868f85383b2b3e73492dad07936f5c282df89"
  integrity sha512-8ZO7qg84TVW0qbRuMsQodLoKUxtkza0a2Vz+/bojekNZIG+CEHNNFgIHsXLSDrg2vlT97rLnrBaAoGUvLikouA==
  dependencies:
    lodash-es "^4.17.21"
    react-cosmos-core "6.0.0-beta.5"
    react-is "^18.2.0" 
    
... 
    

Now we see "Generated cosmos.imports.ts"

$ yarn cosmos
yarn run v1.22.19
$ cosmos --expose-imports
[Cosmos] Using cosmos config found at cosmos.config.json
[Cosmos] See you at http://localhost:5000
[Cosmos] Generated cosmos.imports.ts

[ovidiuch]

@oponder Maybe before when you were on 6.0.0-beta.6 some mismatched canary versions where installed? I've seen this before and it's an annoying issue with the next/canary channels. Because c comes after b if you have a ^x-beta package you might get a x-canary version when you blow up your yarn.lock. For this reason I remove the ^ or ~ signs from beta versions to make sure I pin my dependencies strictly.

[oponder]

Yeah I think that was it, I didn't understand correctly how to set the versions matcher in this case. Thanks for the reply!