Ignite 2.0 EPIC Storyboard

This is the example storyboard of creating a new project in Ignite 2.0

It’s rough work: Feedback welcome @ryanlntn @kevinvangelder @derekgreenberg @jamonholmgren @skellock @fvonhoven

$ ignite new MyAwesomeProject
Welcome to Ignite - The Unfair Headstart Generator
By default all Ignite apps come with Vector Icons, Config, and Animatable.
Would you like to go through our composer? (y/n)
y

The following questions will help us choose your additional goodies.

Would you like the Ignite Development Screens? (y/n)
y

Testing? (use arrow keys)
1. AVA tests with nyc code coverage
2. JEST tests
3. No tests, just madness
1

Would you like I18n support? (y/n)
y

State management? (use arrow keys)
1. Redux
2. MobX (not yet supported, so don't select this)
3. None
1

Redux flow control? (use arrow keys)
1. Sagas
2. Thunk + Sagas (not yet)
3. Async/Await (not yet)
4. None
1

API? (use arrow keys)
1. APISauce
2. Fetch (not yet)
3. None
1

Debugging? (select all that apply)
[ ] Reactotron
[ ] Redux Logger 

Enforce Standard JS on Commit? (y/n)
y

This flow feels natural for me, though I might be blazing past some fundamental questions, and focussing too deeply on others, but let’s see.

The above can be added after the fact with the following: I’ve chosen-kebab-case for Ryan

• ignite add dev-screens
• ignite use ava
• ignite add I18n
• ignite use redux
• ignite use sagas
• ignite use apisauce
• ignite add reactotron
• ignite add redux-logger

[jevakallio]

@GantMan asked me to write up thoughts about Ignite 2.0. Here’s a dump of that conversation:

First thoughts

Generators are a cool idea, definitely something I wanted to do in Pepperoni but never got around to doing. Main pain we wanted to solve with them was that too-unopinionated boilerplates are useless, but more opinionated you get, more people complain about not agreeing with some of them 😃 Letting people pick their opinions à la carte seemed like the best tradeoff.

For generators to be truly useful, they should extend beyond just bootstrapping a new project: Most people don’t necessarily know what they want out of the gate, and they will want to add things to existing projects. To be able to do that, you need to either write a pretty advanced AST-based generator that can identify the right places in the code to inject changes, or to separate the framework part from the userland code and allow modifications to the framework part, à la create-react-app. Have you considered making Ignite more like CRA in that regard?

Pain points

• Programmatically editing .xcodeproj sucks. react-native upgrade becomes useless when you have enough native configurations
• Configuration management (dev, staging, prod) is not obvious to set up, should be included and documented
• Targeting newbies is painful, because if they run into problems they have no idea how to fix them. Piling on ready features on newbies is also dangerous, because if they don’t understand the why, they won’t understand how to effectively use things. Documentation that explains why certain decisions were made is a must if targeting React/Native beginners!

What npm modules should be included?

My opinions on these:

• Library-wise, support everything that Exponent supports.
• Make redux-saga optional (if users want to opt out of saga, include thunk/nothing and let them pick their own - if they know enough to avoid Saga, they’ll know what they want instead)
• Make AVA optional (fall back to Jest which comes out of the box now)
• Make apisauce/reduxsauce optional
• Add optional immutable.js
• Add optional CodePush
• Add optional Fastlane and CI configuration files (e.g. bitrise or travis)

Generator interface

• CLI or a locally-served web-based configuration UI would be good
• Error messages must be first class - what failed, why, and how to work around manually
• Must work on Windows
• Some presets would be good (kitchen sink with example code screens for those who want to understand how things work, and a plain, minimum starting point for those who want to build their own stack)

[fvonhoven]

@GantMan Perhaps an option to choose Navigation? (Native or RNRF)