Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sergey Lapin
    @sergey-lapin
    14 not supported yet, but @skidding said that it will be soon
    Luca Colonnello
    @LucaColonnello
    ok, so by now we can't use it
    Ovidiu Cherecheș
    @skidding
    Good news, just pushed a boilerplate for 0.14! https://twitter.com/skidding/status/667128832554569729
    Josh Perez
    @goatslacker
    I found quite a lot of value in having an easy binary that just setup a project with hot loading given no configuration (or very little) are there any plans on supporting this use case or should I create one based on the latest?
    Ideally, I'd like an easy way to build an interactive playground site or let people clone a repo and have an interactive example they can easily run and play with.
    Ovidiu Cherecheș
    @skidding
    The problem with the binary was that is was very much coupled with your local webpack config, so you'd end up merging bits of your local webpack config into the Cosmos internal webpack config, without having full control over the resulting webpack config used by the playground.
    This became more difficult when Cosmos switched from react-hot-loader to babel-plugin-react-transform, because from what I could tell Babel looks for plugins under current working directory, wheres before I managed to hide dependencies inside the Cosmos package and include them via webpack's resolveLoader option: https://github.com/skidding/cosmos/blob/df29f2051a8619761101920605edfec62edad4f0/component-playground/config.js#L49-L51
    The new boilerplate comes with a "npm run playground" cmd that you can run just as easily once you have everything set up, but I'm curious what do you have in mind. Contributions are definitely appreciated! @goatslacker
    Josh Perez
    @goatslacker
    I'm looking into switching my current project to the new boilerplate right now. Maybe abstracting out the stuff in playground/*.js into an npm I can install. The rest seems pretty standard to me...have a webpack.config and devserver.js
    Ovidiu Cherecheș
    @skidding
    this PR abstracts those files: skidding/cosmos#176
    Ovidiu Cherecheș
    @skidding
    Major change: skidding/cosmos#189 - @goatslacker ended up using your idea to support all React versions at the same time (after seeing cool features added to a 0.13 fork that were never gonna end up in master)
    Josh Perez
    @goatslacker
    very cool, congrats!
    Ovidiu Cherecheș
    @skidding
    @/all wrote an essay on React Cosmos and its evolution, hope you like it: https://twitter.com/skidding/status/796718686631497730
    Sergey Lapin
    @sergey-lapin
    Cosmos with redux - awesome:)
    Gajus Kuizinas
    @gajus
    Hello
    Can anyone explain me the difference from react-storybook ?
    Mattia Occhiuto
    @mattiaocchiuto
    Hi, I was wondering if I can change the fixtures folder name using a config parameter like fixturePaths (what I would achieve is to use a fixtures sub-folder instead of the default __fixtures__) but I did not find a way to do this. I'm thinking about to open a PR where I will add a new config to make the __fixtures__ folder configurable, does it make sense for you?
    Mike Bannister
    @possibilities
    hi all, i need my fixtures to be wrapped in a div with a certain classname on it. so i'm trying to use the html-webpack-plugin but when i run cosmos the fixtures diplayed have this string embedded rather than my the results of the template i'm providing the plugin: /loader/2bbfc63244cae5233fe779fcdcbc9186.html
    ah, got it!
    i had to prevent .html documents from getting processed by file-loader
    Mike Bannister
    @possibilities
    it appears that you can only create fixtures for default exports, is there some way around it?
    Mike Bannister
    @possibilities
    that's a tiny snag, otherwise awesome tool, thanks to whomever works on it!
    reinei
    @reinei
    So, before I open a Issue in the wrong repo:
    I got another error with cosmos, but this time it seems to have to do with the webpack-dev-middleware not wanting to serve my own index.html.
    I am using the HtmlWebpackPlugin in addition to the AddAssetHtmlPlugin (because I am splitting dependencies) and executing a normal dev server works fine, as well as doing a normal compile with webpack.
    However, using cosmos will serve the bundled /static/index.html and will thusly not inject my dependencies into the index.html -> Error on get /
    Ovidiu Cherecheș
    @skidding
    @/all I apologize for neglecting this room. In light of the upcoming 2.0 release, we want to improve communication in the Cosmos community and decided to move the conversation to Slack: https://join-react-cosmos.now.sh/ – See you there!
    Mattia Occhiuto
    @mattiaocchiuto
    Hi, in my project I have some library included as externals in my webpack configuration file. I'd like to know if there is a way to attach that library at the cosmos index page in a way like the one described in this issue react-cosmos/react-cosmos#157
    Zachary Albia
    @zalbia
    Hi, anyone know how to fix "can't resolve" errors? In my case, cosmos couldn't resolve my project files.
    Offending lines are ones like: import Layout from './Layout'