chromaui/chromatic-cli

Broken Action

Closed this issue · 9 comments

jpulec commented

Bug report

The current version of the chromaui/action is busted entirely due to a missing dependency.

Since there's no history in that repository, there's no way to run this action right now.

Error: Cannot find module '@storybook/csf-tools'
Require stack:
- /home/runner/work/_actions/chromaui/action-next/v1/action/register.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/runner/work/_actions/chromaui/action-next/v1/action/register.js:16:16)
    at Module._compile (node:internal/modules/cjs/loader:1105:[14](https://github.com/chromaui/chromatic-cli/actions/runs/5250198366/jobs/9483883311#step:5:15))
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1[15](https://github.com/chromaui/chromatic-cli/actions/runs/5250198366/jobs/9483883311#step:5:16)9:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:8[22](https://github.com/chromaui/chromatic-cli/actions/runs/5250198366/jobs/9483883311#step:5:23):12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/runner/work/_actions/chromaui/action-next/v1/action/register.js'
  ]

Busted CLI run: https://github.com/chromaui/chromatic-cli/actions/runs/5250198366/jobs/9483883311

Osseta commented

We are seeing the same issue across all builds

  • 👍8
CHAOWEICHIU commented

We are seeing the same issue across all builds

  • 👍3
jwwnz commented

We are also seeing the same issue - we didn't see this issue with our builds as late as yesterday

mattseddon commented

@tmeasday any chance this was caused by #755 or (less likely) #756?

tmeasday commented

Thanks folks, I'm looking at this now.

  • 👍1
  • ❤️1
  • 🚀1
tmeasday commented

Ok, I think I fixed the issue, can anyone on action-next give it a try to confirm? @jpulec

tmeasday commented

Ok, I think the issue is resolved with #764, sorry about the delay here, I incorrectly thought our CI checks were telling me the action was working!

  • 👍11
  • ❤️3
jwwnz commented

Working like a charm for us too, thanks for the speedy fix @tmeasday! 🙌

  • ❤️1