Agenda

• News/announcements
• Review previous action items
• Babel config - exclude unnecessary plugins for target browsers react/create-react-app#8030 (@ianschmitz)
• Optional peer dep - Missing peer dependency in react-scripts react/create-react-app#8022 (@ianschmitz)
• v4 - cra.config.js - prior reference from Timer (@mrmckeb)
  • Do we allow service worker customisation?(@mrmckeb)

Attendees

• @iansu
• @ianschmitz
• @mrmckeb

Notes

• Babel config
  • We include plugins that should be excluded by browserslist
    • object spread is one example
• Optional peer dependency on TypeScript
  • Fix this before 3.3 (@iansu)
    • What version? ^3.2.1
• ESLint rule no-unexpected-multiline conflicts with Prettier
  • Disable this rule
    • Add instructions on adding it back in
• v3.3
  • Need to go through PRs and flag any breaking changes
  • Write release notes
• Service worker customization
  • Add a workbox.config.js or make it part of cra.config.js
• Do v4 planning next meeting

Previous Action Items

• Try using GitHub Actions for CI (@iansu)
• Follow up with Google about WebWorker PR (@iansu)
• Talk to Facebook Open Source about T-shirts and swag (@iansu)
• Remove Jack from accounts (@iansu)
• Make sure the team has access to Azure DevOps (@iansu)
• Give people access to Open Collective (@iansu)
• Set up Open Collective (@iansu)
• Add maintainer info to README (@iansu)
• Find out what other projects are using react-dev-utils/openBrowser (@iansu)
• Fix and force-push master (@iansu)
• Don't swallow stack traces on warnings (@gaearon)
• Investigate how other similar projects handle testing (@ianschmitz)
• Lock down force pushing to master (@gaearon)
• Look into enabling canary releases (@ianschmitz)
• Come up with a list of potential Open Collective donors (@iansu)
• Talk to Dan about getting access to the eject survey (@iansu)
• Document triaging process (@iansu)
• Document PR process (@iansu)
• Create maintainer onboarding document (@iansu)

Action Items

• Make PR for TypeScript peer dependency (@iansu)
• Make PR to disable no-unexpected-multiline rule (@iansu)
• Try using GitHub Actions for CI (@iansu)
• Follow up with Google about WebWorker PR (@iansu)
• Talk to Facebook Open Source about T-shirts and swag (@iansu)
• Remove Jack from accounts (@iansu)
• Make sure the team has access to Azure DevOps (@iansu)
• Give people access to Open Collective (@iansu)
• Set up Open Collective (@iansu)
• Add maintainer info to README (@iansu)
• Find out what other projects are using react-dev-utils/openBrowser (@iansu)
• Fix and force-push master (@iansu)
• Don't swallow stack traces on warnings (@gaearon)
• Investigate how other similar projects handle testing (@ianschmitz)
• Lock down force pushing to master (@gaearon)
• Look into enabling canary releases (@ianschmitz)
• Come up with a list of potential Open Collective donors (@iansu)
• Talk to Dan about getting access to the eject survey (@iansu)
• Document triaging process (@iansu)
• Document PR process (@iansu)
• Create maintainer onboarding document (@iansu)

Details

November 27, 2019 10:00am Pacific
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Create+React+App+maintainers+meeting&iso=20191127T18&p1=1440

Zoom: https://zoom.us/j/163553316