I followed the directions, but 'npm start' ended up with an error.

Please see attached log-file.

-- Jeff

npm-debug-log.txt

getting parse error because of missing ) on if statement.

During build browserify -t [reactify --es6] src/App.jsx > build/app.js , I got the following error:

Error: Cannot find module '../utils/LocationsFetcher' from './alt-tutorial/src/actions'

Did you forget to push something?

By following getting started guide I end up with code completely different from this repo.

A getting started guide which doesn't wrap up with a runnable app and points to a repo with different code isn't the best way to document your project, I guess?

Please publish preview using github pages, as I can see u need just create gh-pages branch and publish it

Some have said before and I will echo it again, we need some more complex examples. The quantity of examples listed in the alt README is fantastic but the quality and depth of a practical and re-usable example is lacking.

I know I've read this before somewhere else but feel like the biggest barrier of entry to learning and executing pure flux instead of cultivating community with conventions and best practices is how different each person's implementation feels; following people's walk through and example tours of their implementation is like reading something from Finnegan's Wake. Every implementation leaves either a good or bad taste in your mouth depending on your experience with the pattern.

I think what would be super useful for beginners (including myself) are some practical walk throughs of stuff we run into on a daily basis like auth or how best to leverage frequently used services and what we can do to re-think and re-write the code we carry around with us into something more modular and package-able for everyone else to use.

Feel like alt's greatest strength is also it's greatest weakness since no one stepping up, showing, and sharing with us their actual solutions from project to project. If you're not ending up with more reusable components, services, utils, and, well, files that do something useful for your next project, you should probably just go to redux. Although at this point, I wouldn't blame you for switching to redux for just the community with a clear sense of leadership and direction if you're not getting enough out of each project iteration aside from just an overly complex end result that behaves unexpectedly.

Please update this example for the breaking changes introduced in alt 0.18 (https://github.com/goatslacker/alt/blob/master/CHANGELOG.md#breaking-changes).

Error: Can't walk dependency graph: Cannot find module 'react/addons' from 'C:\git\alt-tutorial\node_modules\alt\components\AltContainer.js'
required by C:\git\alt-tutorial\node_modules\alt\components\AltContainer.js
at C:\git\alt-tutorial\node_modules\resolve\lib\async.js:146:35
at processDirs (C:\git\alt-tutorial\node_modules\resolve\lib\async.js:299:39)
at isdir (C:\git\alt-tutorial\node_modules\resolve\lib\async.js:306:32)
at C:\git\alt-tutorial\node_modules\resolve\lib\async.js:34:69
at FSReqCallback.oncomplete (node:fs:211:21)

I'm having trouble testing when using connectToStores

FWIW, followed your instructions but I had to mkdir build before npm run build would work...

LocationStore.hasError is not defined for the alt-tutorial with cities example and hence throws an error

411bf14 added LocationStore.isLoading() to line 36 of Locations.jsx but there is no matching handler in LocationStore.