You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing a third party CSS the images/files are correctly extracted and versioned during production build, but they're not declared in the manifest.
Steps to reproduce
Create a plain new CRA project;
Add for E.g semantic UI dependency (yarn add semantic-ui-css);
Add the import in the index.js:
import 'semantic-ui-css/semantic.min.css';
Run yarn build;
Expected behavior
Taking for instance the image themes/default/assets/images/flags.png present in the CSS, I would expect it to be in build/static/media/flags.<hash>.png and the reference to be in the manifest.
Actual behavior
The image file with the hash is created:
But the manifest has no trace of it, and actually the entire semantic CSS file is considered as a font file for some reason:
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
Describe the bug
When importing a third party CSS the images/files are correctly extracted and versioned during production build, but they're not declared in the manifest.
Steps to reproduce
yarn add semantic-ui-css
);yarn build
;Expected behavior
Taking for instance the image
themes/default/assets/images/flags.png
present in the CSS, I would expect it to be inbuild/static/media/flags.<hash>.png
and the reference to be in the manifest.Actual behavior
The image file with the hash is created:
But the manifest has no trace of it, and actually the entire semantic CSS file is considered as a font file for some reason:
The text was updated successfully, but these errors were encountered: