1.0.0 Roadmap

Recap

0.10 is going to be one of our largest releases in a long time. We have already merged many changes, let’s recap:

• webpack 2 (native es modules support), tree shaking (yay!)
• (painful) disabled require.ensure
• crash overlay
• resolve localhost proxy on windows
• require proxy starts with http:// or https://
• dynamic import() support
• (painful) whitelist url loader

Long standing PRs we should merge or close

• Networkings docs
• Forking
• Dll (close or figure out how to simplify)

1.0.0

• Jest needs updated
  • Jest 19 upgrade PR
  • Make sure test in src/node_modules/ work
  • Only tests in src/
  • Jest 20
  • Override jest config via https://github.com/facebookincubator/create-react-app/pull/1830 or https://github.com/facebookincubator/create-react-app/pull/1990
• Style lint
  • we should close or figure out what to do with this PR; it’s mainly about enforcing CSS style from what I can gather which is outside of our philosophy of not enforcing style
  • we can postpone this for a second or third release of 0.10, but we should comment on it

• we can largely solve https://github.com/facebookincubator/create-react-app/pull/1616 and https://github.com/facebookincubator/create-react-app/pull/1994 by implementing HOST integration
  • the main problem here is that many of our integrations (e.g. auto reloading) stop working when the application is loaded from a different host, which is mainly caused by our reliance on window.location – if we can make this less painful (by an explicit HOST), we should

• PWA we need to enable progressive web apps
• Code splitting docs
• Crash overlay
  • We need warning support — added the most important one
  • Ignore errors that don’t come from app’s stack
  • Add console.stack to React
  • There is a weird flash when changing from compile error to runtime error
  • If there is a syntax error, sometimes there’s an overlay too because webpack throws on syntax errors for initial bundle
  • We need to linkify messages
• Add docs for local env change (revert https://github.com/facebookincubator/create-react-app/pull/1344/commits/20a0972935cec54a40986bb8417903bab8390b42 and add more info)
  • Make it clear you’re not supposed to use env for real secrets. Maybe add an explanation for why we ignore their FAQ.
• Multiple proxy support (https://github.com/facebookincubator/create-react-app/pull/1790)

Next releases (some possibly 2.0.0, hopefully 1.x)

• require strict module dependence to prevent people from using our internal lodash (https://github.com/facebookincubator/create-react-app/pull/1752)
• Jest debugging support https://github.com/facebookincubator/create-react-app/pull/2041
• Multiple env config files https://github.com/facebookincubator/create-react-app/pull/1344
• Static asset inlining https://github.com/facebookincubator/create-react-app/issues/1944
• Speed up build speed https://github.com/facebookincubator/create-react-app/issues/2037

2.0.0

• Warn when importing unsupported files https://github.com/facebookincubator/create-react-app/issues/1234

• Export render we need to take a hard stance and say we’re not exploring this, or start taking some steps towards it
  • I believe this is something we need to address soon, mainly because Next.js has captured a lot of attention (not that this is bad), but if there’s something we can do to make this better, we should (e.g. multi-entry points)

• External framework integration

• Flow integration

  • webpack plugin
  • Figure out what to do with Windows; currently Flow is suboptimal on Windows (the performance is awful) – we can only enable this integration on macOS for now or disable it all together, but I think we should get the PR in so it doesn’t stagnate

• Development path serving

[Timer]

@williamcolbert Yes, that is covered under “Development path serving”.

[williamcolbert]

@Timer Thank you for the update, will try to give it a shot.