PIMS-394/392/398 Updated vite, vite-plugin-svgr, vitejs/plugin-react #1903
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Summary
PIMS-394
PIMS-392
PIMS-398
vite-plugin-svgr update came with breaking changes to how SVG files are rendered.
OLD
NEW
The reference line must be included for TypeScript to understand what the import is doing. Use it once at the very beginning of any file you use SVGs in.
Changes to Testing
When the imports change to have the
?react
ending, it breaks the way react-scripts & Jest render the SVGs because it cannot find the file with that Vite-specific configuration.To get around this, I added a section the package.json that will look to a newly-created mock SVG for any imports. This means the mock will be seen in the snapshot tests, so those had to be updated. It does mean that we wouldn't be able to test for specific SVGs on screen, but so far that hasn't come up.
🔰 Checklist