-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
feat: storybook-builder and storybook-framework-web-components #2437
Conversation
🦋 Changeset detectedLatest commit: 659ed7e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
I love it! Especially all the docs you've already included 👨🏼🎤 Things I know we need before something like this could land:
Other than the code mostly working for me, I've not looked to closely at it, but once we start getting answers to the above, I am excited to do so! |
logger.warn(`Cannot process ${ext} file with storyStoreV7: ${relativePath}`); | ||
} | ||
|
||
return ` '${toImportPath(relativePath)}': () => import('${process.cwd()}/${relativePath}')`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might need to take care of windows file paths in dynamic imports here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, I'll normalize the right path too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it's actually needed, I checked what happens then in packages/dev-server-rollup/src/rollupAdapter.ts
and seems like the path will be normalized before doing the check which resolves this path correctly, but there are a few checks that are done on the non-normalized one before it which might go wrong
I also doubt now that the left path is normalized good for Windows
I wish I could debug on Windows myself and see if there is a problem and where, but on M1 I can't, so until that I'd rather keep things as is, or I'll have to guess both the problem and solution :D
the long-term plan is to have automated tests and run a Storybook in the build, so I think we can also run one in our Windows pipeline
This looks amazing -- incredible job @bashmish !!! Is there an easy way for me to test this out? |
lol i wrote that "weirdness". Apologies! I'll merge and release a patch to fix if that helps things along. |
@Westbrook Thanks for the compliment!
our own convention for WDS plugins is For the same reason I made a new top section in the documentation, instead of fitting it into the WDS as a subsection. Storybook package naming convention were hard to follow too after moving inside modern-web:
I think @koddsson is busy fixing it
This is also one of my questions in the PR description
I think too early, because some of the features are yet to be implemented, mainly:
Yeah, some TS errors which I didn't have locally. I'll make sure to fix them.
Fully agree on that. Recent issues with 1.x show the urgency for it.
This week I tested the ESM version and couldn't make it work, but I didn't investigate why yet.
Great! I'm open to discuss anything to make sure this is reviewable and goes in the right direction. |
FWIW weirdness fixed here https://github.com/storybookjs/storybook/releases/tag/v7.5.0-alpha.0 |
272248e
to
b69116b
Compare
@Westbrook you can also remove https://github.com/adobe/spectrum-web-components/blob/storybook/patches/%40chialab%2Bestransform%2B0.17.4.patch and update to |
It should all be fixed now |
f313fea
to
9963d96
Compare
lgtm :) |
9963d96
to
d412c84
Compare
d412c84
to
659ed7e
Compare
Fixes #2025
This is mostly a copy of
with renaming, docs restructuring and a few small fixes
Questions
TODOs
npm run update:mjs-dts-entrypoints