It has become apparent that the way I have set up this boilerplate with the router needs some attention so I'm going to be rebuilding it in new branch.

Please keep in mind though this currently works there might be drastic changes!

Sorry, i didn't know where to put these... So i've made this issue

What do you think about adding two more pages, so new people can have more examples to learn from?

I was thinking in there two examples:

• Random Github User (or anything like that): this example would use HTTPDriver. That's nothing really difficult here, the trick would be adding the new source into main without breaking the other existing pages
• Simple Todo app: this example would show more streams that affects the final state like typing, adding a todo, removing a todo and would also generate a more complex view (because you would need a remove button for each todo for example)

I guess the todo app would be more for helping beginners learn rx/cycle... But the first one could be used to show how to add a driver with best practices

What do you think? :)

When a test throws an error , the stack trace is that of the webpacked tes.js file, how do we get testem to print the stack trace based on the source maps?

The runtime build.js works well with source maps .

Very nice and small boilerplate. Exactly what I was looking for to get started with cyclyjs.

One small comment: There's probably no need to load bundle.js as stylesheet.
https://github.com/Cmdv/cycle-webpack-boilerplate/blob/master/index.html#L6

<link rel="stylesheet" href="/build/bundle.js">

hi, i'm a newbie, whats the stndard way to change the port number?

I've noticed the 404 redirection only happen when the string is actual extension of page1 or page2, which mean 404 redirection triggered when you write the url ../page1xx but writing e.g ../page will redirect to index.html. Possible bug in @cycle/history. Are you aware of this @Cmdv ?

While finishing up the browserify boilerplate I am adding the Cycle.js specific linting.

If you want you can add it as well by just doing npm i eslint-config-cycle babel-eslint, adding a .eslintrc, with:

{
  "extends": "eslint-config-cycle",
  "parser": "babel-eslint"
}

And now you can lint your code Cycle-style!

List of tests that need to be made

Component tests

• component is an array
• all components are present
• text of component is correct

Functionality tests

• clicking on nav link displays correct route

We are looking at converting this to use JSX - I have got that working elsewhere in another project.... struggling to achieve the same thing here. How can I for example just amend the Page1 view js file??

running npm start , and then npm test
launches testem but the tests do not run
as far as I can see webpack does not generate the test file

@Cmdv do you have any requirements, preferences on how to tackle this?
Otherwise I'd just go ahead and make a proposal after taking a closer look at your code.

Right now I'm unable to pipe data around the app in a logical way.

Looking at the bulk of the Router here I've had great help from the Cycle community to get to a point where I'm passing data (Counter results) from my home-index and into my the route component.

Where I'm now struggling is being able to subscribe to the CounterState in another part of the app ie: page1 or navbar

My objective is to increment the counter on home and a counter in navbar updates at the same time. When you move to page1 the counter there would reflect the number in the navbar & home.

Any help towards this goal would be greatly appreciated.

I understand that with the upcoming release of Cycle isolated I would be able to just create a single isolated component and put it in different places in the app, but my intention is to try pipe the data through the app as I think this would be more declarative in the long run. Think of situations when you want to build a new page have some of the data shared from another part of the app but you'd also like to adjust that data into a new form.

Using isolate components to pass data around the app is also a bad idea because if you have multiple isolated components then this could be seen as keeping lots of local states.

if you feel the need for a challenge then please send a PR 😄