-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[heft] heft-storybook-react-tutorial "rushx storybook" example does not work #3676
Comments
@octogonz - can you take a look at this? |
Once we get this working again, maybe we can invent a test to prevent this sort of regression in the future. |
This was referenced Nov 28, 2023
This was referenced Mar 23, 2024
This was referenced May 13, 2024
This was referenced May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
In the mainline code we should be able to work with
rushstack/build-tests-samples/heft-storybook-react-tutorial
as the basis for setting up storykit workflow, but the example itself does not successfully build+launch storybook. (This makes it hard to use the example to either set up a new storybook-related project in rush stack, and makes it harder to develop heft improvements for storybook.)Repro steps
Sync latest master code
rush update
rush build
cd to
rushstack/build-tests-samples/heft-storybook-react-tutorial
rushx storybook
Expected result:
Builds and runs storybook: A browser window opens with a storybook Story example.
Actual result:
Produces error output. Does not open the browser.
Details
Verified problem occurs on both my Windows and MacOS machines.
First we see red error output like:
Followed by further indications of the problem:
*Verbose Secondary Errors Here...*
(On our own storybook projects, we've had some troubles with upgrading dependencies and keeping things working lately. The lack of a working example to study certainly compounds the problem. It's been all too easy for other projects to produce similar errors with things like dependency upgrade attempts or attaching additional storybook parts like storyshots.)
I tried to
git bisect
to find where this broke (with the assumption that it ever worked at some point) but had trouble with the process. For now, I'm going to see if I can upgradeheft
for my other ticket by operating the dev heft against our own working storybook project - but hoping someone who's had this project working before can have a look at what's gone wrong with what seems it should be a golden-path example here.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@rushstack/heft
version?node -v
)?The text was updated successfully, but these errors were encountered: