If you are not on v5 yet, we recommend first following the v5 migration guide.
prefer-wait-forwas removedno-wait-for-empty-callbackwas removedawait-fire-eventis now calledawait-async-eventswith support for aneventModuleoption withuserEventand/orfireEventawait-async-eventsis now enabled by default forfireEventin Vue and Marko shared configsawait-async-eventsis now enabled by default foruserEventin all shared configsawait-async-queryis now calledawait-async-queriesno-await-sync-queryis now calledno-await-sync-queriesno-render-in-setupis now calledno-render-in-lifecycleno-await-sync-eventsis now enabled by default in React, Angular, and DOM shared configsno-manual-cleanupis now enabled by default in React and Vue shared configsno-global-regexp-flag-in-queryis now enabled by default in all shared configsno-node-accessis now enabled by default in DOM shared configno-debugging-utilsnow reports all debugging utility methods by defaultno-debugging-utilsnow defaults towarninstead oferrorin all shared configs
- Removing
testing-library/prefer-wait-forif you were referencing it manually somewhere - Removing
testing-library/no-wait-for-empty-callbackif you were referencing it manually somewhere - Renaming
testing-library/await-fire-eventtotesting-library/await-async-eventsif you were referencing it manually somewhere - Renaming
testing-library/await-async-querytotesting-library/await-async-queriesif you were referencing it manually somewhere - Renaming
testing-library/no-await-sync-querytotesting-library/no-await-sync-queriesif you were referencing it manually somewhere - Renaming
testing-library/no-render-in-setuptotesting-library/no-render-in-lifecycleif you were referencing it manually somewhere - Being aware of new rules enabled or changed above in shared configs which can lead to newly reported errors