Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Component imports stopped working in version 3.3.0

See original GitHub issue

import myIcon from '@assets/myIcon.svg?component'; is importing the icon as a url string since version 3.3.0

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:6 (3 by maintainers)

Top GitHub Comments

4reactions

jpkleemanscommented, Jun 16, 2022

I’ve removed the isRootRef check in v3.4.0. So this should be fixed!

3reactions

chriscalocommented, May 9, 2022

Just wanted to confirm that I was running into this in my production builds (even though dev worked perfectly) and updating the vite-svg-loader version to 3.2.x fixed it for me.

Top Results From Across the Web

Auto Import not working in VS code while using Angular 13

While using Angular 13 in VS Code, there is no auto-import while declaring them in a module and when I press Ctrl+space for...

Not able to import "@angular/material" module - Stack Overflow

I have tried importing the above module as import { MatInputModule } from '@angular/material/input'; but then it throws a bunch of error saying ......

5. The import system — Python 3.11.1 documentation

Changed in version 3.3: The import system has been updated to fully implement the second phase of PEP 302. There is no longer...

Traps for the Unwary in Python's Import System

This essay only officially covers Python versions back to Python 2.6. ... While Python 3.3+ is able to import the submodule without any...

node-fetch - npm

A light-weight module that brings Fetch API to node.js. Latest version: 3.3.0, last published: 2 months ago. Start using node-fetch in your ...