Bill Collins

`1.7.12-nightly-20240816.1` has `swc-0.284.0` which _does_ give us the improved errors: ``` ERROR failed to read input source map: failed to find input source map file "index.js.map" in "C:\\Users\\\\git\\\\.yarn\\__virtual__\\-virtual-c44221b7bd\\1\\packages\\baseline\\dist\\components\\icon\\index.js" file as...

@beeequeue I can repro it on my machine - looks like its hanging waiting for user input: ``` Error: Command failed with exit code 1: node /home/bill/git/storybook/code/lib/create-storybook/bin/index.cjs init --yes --skip-install...

Running the command it claims to be running (`node /home/bill/git/storybook/code/lib/create-storybook/bin/index.cjs init --yes --skip-install`) in the sandbox directory does work, but fails for some reason in task. cwd is correct ,and...

As far as I can tell, find-up treats stopAt as inclusive, but empathic treats it as exclusive, hence the failure to detect the webpack.config.js. Quite why it seems to work...

There's now a new prerelease of empathic (`2.0.0-next.0`) that replaces the exclusive `stop` parameter with an inclusive `last` parameter. This matches more closely the behaviour of `find-up` and so should...

O no more conflicts! Possibly an unwelcome distraction, but I did notice a few users of `fd-package-json` (some adjacent to `find-up`!), which is an opportunity to cull another couple of...

@ndelangen this is all looking mighty green now except for the flaky unit test?

I wasn't sure on this - after all, the spec is rather light on the expected output format, that are configurable in postcss, lightningcss and others - such as how...

So what we're stuck on now is that `tsup` appears to be stripping the `@ts-expect-error` comments that are attached to types that form part of storybook's API. We could remove...

The addon-vitest one is curious, looks like tsup can't handle nodenext module resolutions?