You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried deleting node_modules folder and pnpm-lock.yaml file, running bit clear-cache && bit capsule delete --all && bit install e.t.c but I still get the same error.
Tagging and exporting the components works fine and I can see the preview on bit.cloud but it doesn't work on development server
The text was updated successfully, but these errors were encountered:
Describe the bug
When I create a custom tailwind env (via this article on bit https://bit.dev/blog/integrating-tailwind-css-and-bit-for-component-styling-lgntqstt/#live-playground-support), I set my UI components to use the env, and then I run the
![image](https://private-user-images.githubusercontent.com/68024640/239873913-1aa1583a-7118-41fb-ac97-19d9f6efc968.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2MDA5ODcsIm5iZiI6MTcyNTYwMDY4NywicGF0aCI6Ii82ODAyNDY0MC8yMzk4NzM5MTMtMWFhMTU4M2EtNzExOC00MWZiLWFjOTctMTlkOWY2ZWZjOTY4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA2VDA1MzEyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ4ZjEzM2E2YTJiM2UzNDA0ZDI0NWYzZTBjNmE5NTExYWMzOWVmZTY3YWU4Yzg5M2Q2YTZmZjBhODVmMjU3YmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.CVuWMmdnuAvQ9Z525KQYbMqKtvoZNoGcEmd4bVLxTwU)
bit start
, the preview and overview of the components don't work and I get this error:Expected Behavior
Seeing my react component overview and previews
Screenshots, exceptions and logs
Specifications
for harmony workspace
Additional context
node_modules
folder andpnpm-lock.yaml file
, runningbit clear-cache && bit capsule delete --all && bit install
e.t.c but I still get the same error.The text was updated successfully, but these errors were encountered: