docs: removing reference to SVGR ReactComponent

README.md

@@ -136,8 +136,7 @@ Then, create a `src/__mocks__` folder and add the necessary mocks.
 **svg.js:**
 
 ```
-export default 'SvgrURL';
-export const ReactComponent = 'SvgMock';
+module.exports = 'SvgURL';
 ```
 
 **file.js:**
@@ -146,7 +145,7 @@ export const ReactComponent = 'SvgMock';
 module.exports = 'FileMock';
 ```
 
-You can change the values of "SvgrURL", "SvgMock", and "FileMock" if you want to reduce changes necessary to your snapshot tests; the old values from frontend-build assume svg is only being used for icons, so the values referenced an "icon" which felt unnecessarily narrow.
+You can change the values of "SvgURL", and "FileMock" if you want to reduce changes necessary to your snapshot tests; the old values from frontend-build assume svg is only being used for icons, so the values referenced an "icon" which felt unnecessarily narrow.
 
 This is necessary because we cannot write a tsconfig.json in MFEs that includes transpilation of the "config/jest" folder in frontend-base, it can't meaningfully find those files and transpile them, and we wouldn't want all MFEs to have to include such idiosyncratic configuration anyway.  The SVG mock, however, requires ESModules syntax to export its default and ReactComponent exports at the same time.  This means without moving the mocks into the MFE code, the SVG one breaks transpilation and doesn't understand the `export` syntax used.  By moving them into the MFE, they can be easily transpiled along with all the other code when jest tries to run.
 

cli/test-app/src/__mocks__/file.js

@@ -1 +1 @@
-module.exports = 'FileMock';
+export default 'FileMock';

cli/test-app/src/__mocks__/svg.js

@@ -1,2 +1 @@
 export default 'SvgURL';
-export const ReactComponent = 'SvgMock';