1.0 checklist

[threepointone]

Main task to track some things we discussed that we should do before getting to 1.0:

• Write a document for converting a create-react-app repository/project into a modular repository.  #115 Write a document for converting a create-react-app repository/project into a modular repository.
• the default app template shouldn't look like the CRA default view #58 the default app template shouldn't look like the CRA default view
• Generate nicer READMEs inside new projects/apps/views/packages.  #144 Generate nicer READMEs inside new projects/apps/views/packages.
• What does the modular upgrade experience look and feel like? #110 What does the modular upgrade experience look and feel like?
• Library builds: Umbrella issue #253 Library builds: Umbrella issue
• E2E tests #48 E2E tests
• RFC: Incremental builds stage 1 - rebuilding affected packages/apps.  #147 affected builds
• export modular.tsconfig #60 export modular.tsconfig (PR, PR)
• Fix tests, but actually this time.  #169 Fix tests, but actually this time. (PR)
• update to create-react-app 4.0 #128 update to create-react-app 4.0 (PR)
• export modular-views.macro #59 export modular-views.macro (PR)
• Fix package.json in eslint-config-modular-app #42 Fix package.json in eslint-config-modular-app (PR)
• modular should tell you when it's out-of-date #133 modular should tell you when it's out-of-date (PR)
• add .editorconfig to generated repos #68 add .editorconfig to generated repos (PR)
• discussion: modular for libs  #49 modular for libs (PR)
• enable in-browser linting experience #136 enable in-browser linting experience (PR)
• modular test script does not run sub-package test #130 modular test script does not run sub-package test (PR)
• react/react-dom (and other core dependencies) should be installed at the root  #149 react/react-dom (and other core dependencies) should be installed at the root (PR)
• Freshly generated project has broken test on Windows #151 Freshly generated project has broken test on Windows (PR)
• creating a new view/package doesn't replace the stub names with the new view/package name  #156 creating a new view/package doesn't replace the stub names with the new view/package name (PR)

---

Further, there's a discussion to be had about a website and examples, but we'll get to that as well.

[matt-d-webb]

@threepointone Thank you for this consolidated list.