ivan-kleshnin/cyclejs-examples

CycleJS examples

About Me

Experienced software engineer, entrepreneur, polymath. Cofounder of DevScanr.com and Paqmind.com.

My professional interests include:

• 🎓 Computer Science and Data Science
• 🕸️ Web Development
• 🏗️ System and Software Architecture
• 🔮 Functional and Reactive Programming
• 🧩 Static Types
• 🔘 UI/UX

My working preferences are minimalism and 改善 (kaidzen, continuous improvement).

cyclejs-examples's Issues

Update to Ramda 0.18

gulp default task fails

I cloned the repo, did npm install, then ran gulp and I got this error:

$ gulp
[gulp] Using gulpfile ./gulpfile.js
[gulp] Starting 'default'...
[gulp] Starting 'dist-html'...
[gulp] Starting 'dist-css'...
[gulp] Starting 'dist-less'...
[gulp] Finished 'dist-less' after 84 μs
[gulp] Finished 'default' after 13 ms
[gulp] Finished 'dist-css' after 63 ms
[gulp] Finished 'dist-html' after 73 ms
[gulp] Starting 'build'...
[gulp] Finished 'build' after 226 ms
[gulp] Starting 'bundle-vendors'...
[gulp] Finished 'bundle-vendors' after 5.65 ms
[gulp] Starting 'prebundle-apps'...
[gulp] Finished 'prebundle-apps' after 15 ms
[gulp] Starting 'bundle-apps'...
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at WriteStream.EventEmitter.once (events.js:185:8)
    at Socket.Readable.pipe (_stream_readable.js:541:8)
    at ./gulpfile.js:97:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at WriteStream.EventEmitter.once (events.js:185:8)
    at Socket.Readable.pipe (_stream_readable.js:541:8)
    at ./gulpfile.js:98:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at Socket.Readable.pipe (_stream_readable.js:476:8)
    at ./gulpfile.js:97:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at ./node_modules/gulp/node_modules/orchestrator/index.js:279:18
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at Socket.Readable.pipe (_stream_readable.js:491:8)
    at ./gulpfile.js:97:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at ./node_modules/gulp/node_modules/orchestrator/index.js:279:18
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at WriteStream.EventEmitter.once (events.js:185:8)
    at Socket.Readable.pipe (_stream_readable.js:536:8)
    at ./gulpfile.js:97:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at Socket.Readable.pipe (_stream_readable.js:476:8)
    at ./gulpfile.js:98:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at ./node_modules/gulp/node_modules/orchestrator/index.js:279:18
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at Socket.Readable.pipe (_stream_readable.js:491:8)
    at ./gulpfile.js:98:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at ./node_modules/gulp/node_modules/orchestrator/index.js:279:18
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at WriteStream.EventEmitter.addListener (events.js:160:15)
    at WriteStream.Readable.on (_stream_readable.js:689:33)
    at WriteStream.EventEmitter.once (events.js:185:8)
    at Socket.Readable.pipe (_stream_readable.js:536:8)
    at ./gulpfile.js:98:20
    at Array.forEach (native)
    at Gulp.<anonymous> (./gulpfile.js:89:8)
    at module.exports (./node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (./node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (./node_modules/gulp/node_modules/orchestrator/index.js:214:10)
[gulp] Finished 'bundle-apps' after 62 ms
[gulp] Starting 'watch-src'...
[gulp] Finished 'watch-src' after 55 ms
[gulp] Starting 'watch-build'...
[gulp] Finished 'watch-build' after 23 ms

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

1.6-form proposal

I would like to see a form example involving dynamically loaded/populated form fields. Such as a list of area codes that update based on selected country or state, or a list of street names that update based on postal (zip) code.

Ideally these filtered values would be fetched asynchronously from the server which would add additional complexity to the form. I would be very interested to see how you would tackle this in cycle.js

Thanks

Fix CRUD example

We have bugs due to the absence of shrinkwrap.json

Usage of startWith is incorrect

...in progress

Error on runing npm run build

λ npm run build

[email protected] build C:\Users\Admin\Desktop\RxJS\CYCLE-FRAMEWORK\cyclejs-examples-master
webpack --config webpack.config-prod.js --progress --colors

C:\Users\Admin\Desktop\RxJS\CYCLE-FRAMEWORK\cyclejs-examples-master\webpack.config-prod.js:2
import Path from "path";
^^^^^^
SyntaxError: Unexpected reserved word
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:427:25)
at Object.Module._extensions..js (module.js:462:10)
at Module.load (module.js:339:32)
at Function.Module._load (module.js:294:12)
at Module.require (module.js:349:17)
at require (module.js:368:17)
at module.exports (C:\Users\Admin\Desktop\RxJS\CYCLE-FRAMEWORK\cyclejs-examples-master\node_modules\webpack\bin\convert-argv.js:56:13)
at Object. (C:\Users\Admin\Desktop\RxJS\CYCLE-FRAMEWORK\cyclejs-examples-master\node_modules\webpack\bin\webpack.js:54:40)
at Module._compile (module.js:444:26)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\iojs\node.exe" "C:\Program Files\iojs\node_modules\npm\bin\npm-cli.js" "run" "build"
npm ERR! node v1.5.0
npm ERR! npm v2.7.0
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: webpack --config webpack.config-prod.js --progress --colors
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script 'webpack --config webpack.config-prod.js --progress --colors'.
npm ERR! This is most likely a problem with the cyclejs-examples package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! webpack --config webpack.config-prod.js --progress --colors
npm ERR! You can get their info via:
npm ERR! npm owner ls cyclejs-examples
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Admin\Desktop\RxJS\CYCLE-FRAMEWORK\cyclejs-examples-master\npm-debug.log

#3.3 Slider: multiple. Bug with removing

Hi!

I think i found the bug, can you recheck? Try this sequence:

1. Update the page and remove first and single element on page
2. Add new element
3. Try to remove this new element >> it will not work
4. Add another element >> now you can remove them both

Add comments about shareReplay

...in progress

Rewrite with new CycleJS API

#3.4 update HTML

Hello!

I'm sorry if i'm asking silly question.
I don't understand this example: #3.4 Slider: colors

Nothing happens by changing "Amount" input:
http://puu.sh/gKA0h.png
http://puu.sh/gKA27.png

File with list of examples

Can we have this?

Thanks a billion!

Two things:

First, reading through your repo my jaw dropped at the beauty of this approach. I have been searching for a simple, unified, flexible way to make interfaces and it feels like another really nice step toward that.

Second, I first learned about cycle many months ago through your comments on baobab, so thanks for that too! Yomguithereal/baobab#145

Best,
Jesse

Improve styles & markup

Need more accurate layouts with minal investments.

Update to Eslint 1.0

Webpack

Requires JSX loader. Track cyclejs/cyclejs#35

Some code conventions

Hi, first of all, I have to say I really like this repo. It's taking shape as a really good reference of examples.

In the code I noticed the tendency to write

let DOM = Cycle.createDOMUser("main");
DOM.inject(View).inject(Model).inject(Intent).inject(DOM);

But I think it's very harmful for framework learners the name "DOM", since the actual meaning of this variable is really "user". I recommend calling it "domUser" or just "user". The idea is that the actual user is a DataFlowNode (input is the view, output is the interaction events). That's what a real human does with a user interface: it sees it (view) and it interacts with it (events).

routing 2.2

I'm a beginner in cyclejs, so sorry for maybe dumb questions. And my english)
I'm searching routing solutions. Encore i'm looking for answer on question: "Can i create spa with cyclejs".
I tried to use cyclic-router, everything is working, but page is always refreshing on click link. I.e. as i think it's not spa approach.
Later i found your repository and examples in routing. I thought that I found what I was looking for. But i found one detail: when i refresh page in "some_link" in app, server gives me "Cannot GET /some_link".
Can you explain me why it causes and tell how to create spa using cyclejs?