-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Export mode conflict between backgrounds plugins and storybook (TailwindCSS) #9769
Comments
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Up to avoid closing. Do you have any feedback/question about this? |
Another use case on a story using tailwind config:
Got:
I don't think this is related to my config file. Currently, it's required on svelte file without any error. |
The issue seems to come from this code block of tailwind.config.js: let customColors = Object.assign(colors, {
green: makeColor('#48d3aa'),
orange: makeColor('#ff9e00'),
yellow: makeColor('#ffe000'),
purple: makeColor('#5f4ae3'),
teal: makeColor('#0b7d89'),
pink: makeColor('#ffabb7'),
gray: makeColor('#43414E', 900),
}); |
Also tried: let customColors = Object.assign(colors, {}); And even:
It seems |
Applied #5298 (comment), works well. |
Describe the bug
I'm trying to export my TailwindCSS configuration colors.
To Reproduce
The WIP is on this open-source MR: https://gitlab.com/nexylan/design/-/merge_requests/29
npm install && npm run storybook
TypeError: "exports" is read-only
Expected behavior
Working. :-)
This is because of the export tag of
tailwind.config.js
:But if I replace it by
export default {
, I have this storybook runtime error:System:
Please paste the results of
npx -p @storybook/cli@next sb info
here.Additional context
All the code source are on the opened MR. :-)
I'm not sure of the source of the issue, so don't hesitate to comment if you need more details. 👍
The text was updated successfully, but these errors were encountered: