Comments (4)
ovidiuch
commented on June 17, 2024
1
@FrancoRATOVOSON You're using mismatching versions of Cosmos packages.
Make this change in your package.json:
Delete .parcel-cache, then restart Cosmos and your multi-fixture should look fine.
from react-cosmos.
FrancoRATOVOSON
commented on June 17, 2024
1
Worked perfectly fine 👌🏾 thanks
from react-cosmos.
ovidiuch
commented on June 17, 2024
@FrancoRATOVOSON Everything looks good to me in your example. Maybe the dev server stopped building and is out of date due to some error I'm not seeing. I can investigate for you if you have a public repo that reproduces this issue.
from react-cosmos.
FrancoRATOVOSON
commented on June 17, 2024
@skidding here's the repos https://github.com/FrancoRATOVOSON/e-commerce/tree/shadcn-migration
It's not a production app, just to try technos, so sorry for the mess.
Everything is inside packages/ui on this branch.
from react-cosmos.
Related Issues (20)
- Setup of React Native not clear HOT 3
- Can't change webpack.output.publicPath via cosmos.webpack.js HOT 2
- Live demo is not working HOT 1
- The top-level-await experiment is not enabled (set experiments.topLevelAwait: true to enabled it) HOT 5
- Increase awareness of the ability to override Webpack config HOT 1
- Webpack emits DefinePlugin warning on a fresh install with create-react-app HOT 2
- Unable to get started with vite plugin following the setup docs HOT 10
- Props tab show nothing when decorator for fixture not include `children` in response HOT 7
- Alert shows the wrong port number (minor) HOT 2
- Cosmos cannot find Vite configuration file with "ts" extension HOT 4
- Respect SSL option when connecting to websocket HOT 4
- fixture fails to enter fullscreen mode HOT 6
- Can't get cosmos to run with or without babel-loader or ts-loader HOT 4
- `cosmos --expose-imports` seems to have stopped building imports at some point HOT 3
- Cosmos.imports.ts isn't created nor updated on subsequent runs of npm run cosmos HOT 3
- Unable to use alias Preact in `next` branch HOT 9
- Fixture Error : Lazy element type must resolve to a class or function HOT 3
- Build fails with node@20 HOT 4
- Next.js 14 no longer allows 'use client' and generateStaticParams() to be used together HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react-cosmos.