New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: IonIcons not loading after parcel build #1215
Comments
Thanks for the issue! This issue has been labeled as Please reproduce this issue and provide a way for us to access it (GitHub repo, StackBlitz, etc). Without a reliable code reproduction, it is unlikely we will be able to resolve the issue, leading to it being closed. If you have already provided a code snippet and are seeing this message, it is likely that the code snippet was not enough for our team to reproduce the issue. |
I tried a quick Parcel build with Ionicons (and nothing else), and the icons loaded for me. Please provide a full reproduction so we can see what's different about your setup. Thanks. |
Hi, The ion icons are not loading in dev server (localhost) when Im running npm run start , they are loading in build but with no styles or colour to them. Launch the dev server with npm run start and icons are not loading |
Hi. were you able to reproduce the issue ? |
HI Team, any updates on above |
Current Behavior
IonIcons not loading after parcel build
Expected Behavior
Icons should load
I am using ionicons for my html. It is working fine with live server. I tried to build with parcel and now they are not loading. icons are loading in network tab but not showing up in build. Please advise. Assume body tag enclosed for html
live server
parcel build
console is giving this error : Uncaught SyntaxError: Cannot use import statement outside a module (at ionicons.esm.js:1:1)
sample code
<style> .feature-icon { color: #c92a2a; height: 3.6rem; width: 3.6rem; margin-bottom: 2.4rem; } ### Steps to Reproduce Build with parcel with ion-icons ### Code Reproduction URL _No response_ ### Additional Information _No response_The text was updated successfully, but these errors were encountered: