Skip to content
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

Ensure preview annotations are resolved relative to the cwd #19594

Merged
merged 2 commits into from
Oct 25, 2022

Conversation

tmeasday
Copy link
Member

Issue: (when sandbox running in v6 mode, although this was a more general issue):

Pasted Graphic

What I did

Make entry point filenames not have / in them.

How to test

Run v6 sandbox. Note it won't run (2nd PR coming) but it should start.

@tmeasday tmeasday added bug patch:yes Bugfix & documentation PR that need to be picked to main branch core builder-webpack5 labels Oct 24, 2022
@tmeasday tmeasday changed the title Ensure preview annotatios are resolved relative to the cwd Ensure preview annotations are resolved relative to the cwd Oct 24, 2022
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we get some kind of test for this?

@@ -125,21 +125,24 @@ export default async (
path.join(__dirname, '..', '..', 'templates', 'virtualModuleEntry.template.js')
);

previewAnnotations.forEach((previewAnnotationFilename: any) => {
previewAnnotations.forEach((previewAnnotationFilename: string | undefined) => {
if (!previewAnnotationFilename) return;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When does this exit early?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No idea. Previously it was just being cast to any and then used as a string

@tmeasday
Copy link
Member Author

I don't think we have any meaningful tests for generated webpack configs, outside of running the Storybook. So the test would be getting a v6 store sandbox.

@tmeasday tmeasday merged commit 01448bc into next Oct 25, 2022
@tmeasday tmeasday deleted the tom/sb-849-cant-run-the-v6-store-in-sandboxes branch October 25, 2022 04:46
@shilman shilman added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug builder-webpack5 core patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants